Re: pgsql: Attempt to fix unstable regression tests, take 2 - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Attempt to fix unstable regression tests, take 2
Date
Msg-id 11757.1585619115@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Attempt to fix unstable regression tests, take 2  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Attempt to fix unstable regression tests, take 2  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
I wrote:
> Specifically, I notice that in the last couple of failures involving
> tests on "mcv_lists", we are considering stats on a 5000-row table.
> With the standard setting default_statistics_target = 100, ANALYZE
> will take a 3000-row random sample, meaning that its results are
> *inherently* not 100% reproducible.

No, wait, scratch that --- I misremembered the multiplier.  Actually
ANALYZE will try to acquire a 30000-row sample, so its sample *should*
always include the entire table.  Autovacuum or not, the stats ought
to come out exactly the same every time in this test case.  But they
are not doing so, at least on some machines.  We need to figure out
why that is.

Anyway, I remain suspicious that the instability is the fault
of something in the statistics code, not of autovacuum.

            regards, tom lane



pgsql-committers by date:

Previous
From: Peter Geoghegan
Date:
Subject: pgsql: Further simplify nbtree high key truncation.
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Attempt to fix unstable regression tests, take 2