| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: issue with track_commit_timestamp and server restart |
| Date: | 2016-10-24 12:52:16 |
| Message-ID: | 20161024125216.46nak4iwltdvnpqm@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Craig Ringer wrote:
> I initially could'n't see this when tested on 8f1fb7d with a
> src/test/recovery/t test script. But it turns out it's OK on immediate
> shutdown and crash recovery, but not on clean shutdown and restart.
Oh, oops.
> The attached patch adds a TAP test to src/test/recovery to show this.
I moved it to src/test/modules/commit_ts and pushed. src/test/recovery
is not currently run by buildfarm, except hamster, unless the bf client
has been patched since I last looked. But that's not the reason I moved
it, but rather because the other location seemed better. I also fixed
the wrongly pasted comment at the top of the file while at it.
If this disrupts the buildfarm in any way I will just revert it
immediately.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-10-24 13:08:24 | Re: issue with track_commit_timestamp and server restart |
| Previous Message | Tom Lane | 2016-10-24 12:44:44 | Re: On conflict update & hint bits |