Re: expected/sequence_1.out obsolete? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: expected/sequence_1.out obsolete?
Date
Msg-id 14013.1413929454@sss.pgh.pa.us
Whole thread Raw
In response to expected/sequence_1.out obsolete?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> expected/sequence_1.out hasn't been updated at least since
> commit d90ced8bb22194cbb45f58beb0961251103aeff5
> Date:   Thu Oct 3 16:17:18 2013 -0400
> and nobody appears to have complained.

> Can it be removed?

No, it needs to be fixed.  The alternate output from "select * from
foo_seq" will appear occasionally (from memory, if a checkpoint starts
or perhaps completes during the test).

We might have noticed this already if the buildfarm weren't so noisy
lately :-(

An alternative answer would be to remove log_cnt from the set of
columns displayed, but I think that would be taking away part of the
point of that particular test.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables
Next
From: Michael Paquier
Date:
Subject: Re: expected/sequence_1.out obsolete?