| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: expected/sequence_1.out obsolete? |
| Date: | 2014-10-21 22:10:54 |
| Message-ID: | 14013.1413929454@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2014-10-21 22:15:32 | Re: expected/sequence_1.out obsolete? |
| Previous Message | Jeff Janes | 2014-10-21 21:36:58 | Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables |