From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Autovacuum-induced regression test instability |
Date: | 2019-04-15 17:22:30 |
Message-ID: | 17428.1555348950@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
In connection with the issue discussed at [1], I tried to run
the core regression tests with extremely aggressive autovacuuming
(I set autovacuum_naptime = 1s, autovacuum_vacuum_threshold = 5,
autovacuum_vacuum_cost_delay = 0). I found that the timestamp
test tends to fail with diffs caused by unstable row order in
timestamp_tbl. This is evidently because it does a couple of
DELETEs before inserting the table's final contents; if autovac
comes along at the right time then some of those slots can get
recycled in between insertions. I'm thinking of committing the
attached patch to prevent this, since in principle such failures
could occur even without hacking the autovac settings. Thoughts?
regards, tom lane
[1] https://www.postgresql.org/message-id/15751.1555256860%40sss.pgh.pa.us
Attachment | Content-Type | Size |
---|---|---|
make-timestamp_tbl-row-ordering-stable.patch | text/x-diff | 968 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2019-04-15 17:32:54 | Re: Zedstore - compressed in-core columnar storage |
Previous Message | Tom Lane | 2019-04-15 17:13:01 | Re: New vacuum option to do only freezing |