From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Autovacuum-induced regression test instability
Date: Tue, 16 Apr 2019 11:08:06 -0400
Message-ID: <28186.1555427286@sss.pgh.pa.us> (raw)
In-Reply-To: <20190416055312.GG2673@paquier.xyz>
References: <17428.1555348950@sss.pgh.pa.us>
<20190416055312.GG2673@paquier.xyz>
Michael Paquier <michael@paquier.xyz> writes:
> Aren't extra ORDER BY clauses the usual response to tuple ordering? I
> really think that we should be more aggressive with that.
I'm not excited about that. The traditional argument against it
is that if we start testing ORDER BY queries exclusively (and it
would have to be pretty nearly exclusively, if we were to take
this seriously) then we'll lack test coverage for queries without
ORDER BY. Also, regardless of whether you think that regression
test results can be kicked around at will, we are certainly going
to hear complaints from users if traditional behaviors like
"inserting N rows into a new table, then selecting them, gives
those rows back in the same order" go away. Recall that we had
to provide a way to disable the syncscan optimization because
some users complained about the loss of row-ordering consistency.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, michael@paquier.xyz, pgsql-hackers@lists.postgresql.org
Subject: Re: Autovacuum-induced regression test instability
In-Reply-To: <28186.1555427286@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox