Re: Postgresql 9.5 committing and log sequence number
От | Albe Laurenz |
---|---|
Тема | Re: Postgresql 9.5 committing and log sequence number |
Дата | |
Msg-id | A737B7A37273E048B164557ADEF4A58B5397BAF8@ntex2010i.host.magwien.gv.at обсуждение исходный текст |
Ответ на | Postgresql 9.5 committing and log sequence number (Poul Kristensen <bcc5226@gmail.com>) |
Ответы |
Re: Postgresql 9.5 committing and log sequence number
|
Список | pgsql-admin |
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
В списке pgsql-admin по дате отправления: