Re: expected/sequence_1.out obsolete?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: expected/sequence_1.out obsolete?
Date: 2014-10-21 22:27:20
Message-ID: 15003.1413930440@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> I don't think that this is a good idea, have a look at bb3f839 explaining
> that this alternate output may happen when a checkpoint kicks in. Simple
> patch is attached.

Pushed, thanks. (The 9.4 branch was broken too, but differently :-()

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabrízio de Royes Mello 2014-10-21 22:29:13 Re: Simplify calls of pg_class_aclcheck when multiple modes are used
Previous Message Jim Nasby 2014-10-21 22:25:58 Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables