Re: issue with track_commit_timestamp and server restart

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Álvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Subject: Re: issue with track_commit_timestamp and server restart
Date: 2016-10-24 05:08:16
Message-ID: CAMsr+YHJ2PN8FP_fjSCM3LGP9ACiFjVFSuggUvhwSxZjuk=sVA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 24 October 2016 at 12:58, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:

> The attached patch adds a TAP test to src/test/recovery to show this.

Added to CF.

https://commitfest.postgresql.org/11/834/

... but IMO this should go in the next bugfix release.

I've also applied nearly the same fix for the same bug in the original
commit timestamp implementation in the BDR Postgres tree.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-10-24 05:46:43 Re: pg_basebackup stream xlog to tar
Previous Message Michael Paquier 2016-10-24 05:04:17 Re: issue with track_commit_timestamp and server restart