Re: Postgresql 9.5 committing and log sequence number

From: Poul Kristensen <bcc5226(at)gmail(dot)com>
To: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Postgresql 9.5 committing and log sequence number
Date: 2016-11-15 12:49:33
Message-ID: CAAOuvVrCoGj6aC3Cr7nu6d=A+adq1mqrviEiG9MjyeyCq03G6Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Thanks a lot for fast responce.

How come that repeating
SELECT txid_current();
makes 1 added to xid
shown by
select * from pg_last_committed_xact();

repeating
select * from pg_last_committed_xact();
does not add 1 for each repeat of
select * from pg_last_committed_xact();

2016-11-11 12:56 GMT+01:00 Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>:

> Poul Kristensen wrote:
> > I/we use replication
> > Sender and receiver process is showing the log sequence
> > number.
> > I assume that the log sequence is changing after every commit of an
> update or more updates.
> > I assume that the archive log is changing after every commit of an
> update or
> > more updates.
> >
> > Going to test a PITR I need to know where to look for the log sequence
> number after PITR.
>
> The log sequence number is not a good way to measure the success of PITR,
> since after a successful PITR PostgreSQL will switch to a new time line,
> and the log sequence will change.
>
> Two ideas:
> - Get the transaction ID with
> SELECT txid_current();
> You can use that with the "recovery_target_xid" parameter in
> recovery.conf.
>
> - Use pg_create_restore_point() to create a restore point and use that with
> "recovery_target_name" in recovery.conf.
>
> Yours,
> Laurenz Albe
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Albe Laurenz 2016-11-15 13:13:26 Re: Postgresql 9.5 committing and log sequence number
Previous Message John Scalia 2016-11-14 22:37:07 Re: hostnossl in pg_hba.conf demands a password