On Thu, Oct 29, 2015 at 5:41 PM, Fujii Masao <masao.fu...@gmail.com> wrote:
> I found another strange behavior on track_commit_timestamp.
> Here are the steps to reproduce it.
> 1. Start the master and standby servers with track_commit_timestamp enabled.
> Since committs is activated in standby, pg_last_committed_xact() can
> successfully return the timestamp of last transaction as expected.
> 2. Disable track_commit_timestamp in the master and restart the master server.
> The parameter-change WAL record is streamed to the standby and committs
> is deactivated. pg_last_committed_xact() causes an ERROR in the standby.
> 3. Run checkpoint in the master.
> 4. Run restartpoint in the standby after the checkpoint WAL record generated
> in #3 is replicated to the standby.
> 5. Restart the standby server.
> Committs is activated in the standby because track_commit_timestamp is
This seems wrong already at this point.
The Enterprise PostgreSQL Company
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: