Tom Lane wrote:
> Alvaro Herrera writes:
> > Mart�n Marqu�s wrote:
> >> This really gives little use for recovery_target_xid. :(
>
> > Hmm, you can still use pg_xlogdump to figure it out from the actual WAL,
> > which has the correct XIDs. It's obviously a worse solution though from
> > the user
Alvaro Herrera writes:
> Martín Marqués wrote:
>> This really gives little use for recovery_target_xid. :(
> Hmm, you can still use pg_xlogdump to figure it out from the actual WAL,
> which has the correct XIDs. It's obviously a worse solution though from
> the user's POV, because it's hard to f
Martín Marqués wrote:
> El 10/02/16 a las 21:46, Tom Lane escribió:
> > We could maybe fix this by redefining %x as "the current or most recent
> > xid", so that it'd still be valid for messages issued post-commit.
> > But I'm afraid that would add about as many bad behaviors as it would
> > remov
El 10/02/16 a las 21:46, Tom Lane escribió:
>
> Think you're outta luck on that. If we logged the duration before
> commit, it would be entirely misleading for short commands, because
> the time needed to commit wouldn't be included. So we log it after,
> when there's no longer any active transa
El 10/02/16 a las 20:11, Adrian Klaver escribió:
>>
>> So, my question is: Is this a bug, or a feature? I recall being able to
>> log xids on DDLs but can't find the correct settings now.
>
> Maybe?:
>
> %v Virtual transaction ID (backendID/localXID)
AFAICS that value won't help if I need th
=?UTF-8?Q?Mart=c3=adn_Marqu=c3=a9s?= writes:
> [ log_line_prefix %x frequently reports zero ]
> <2016-02-10 17:41:19 EST [5729]: [1] xid=0
> db=data,user=postgres,app=psql,client=[local]>LOG: duration: 17.242 ms
> statement: create table test_xid (id int);
> <2016-02-10 17:41:21 EST [5729]: [2]
On 02/10/2016 02:58 PM, Martín Marqués wrote:
Hi,
I've been fooling around on a test environment where I wanted to run
some PITR tests using recovery_target_xid.
So I started setting up postgresql.conf with log_statement='ddl' (and
'mod' also) and the %x placeholder in log_line_prefix:
Odd res
Hi,
I've been fooling around on a test environment where I wanted to run
some PITR tests using recovery_target_xid.
So I started setting up postgresql.conf with log_statement='ddl' (and
'mod' also) and the %x placeholder in log_line_prefix:
Odd result was that I always got a zero as the xid.
S
