diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2019-09-27 11:28:25 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2019-09-27 11:28:25 -0400 |
| commit | e40f3c7472036f5a06897a11ac79fd26ec2ccf7d (patch) | |
| tree | 2c660d4841b24046e0aa4d615843d004f3bc8664 /src/include/executor | |
| parent | b34bc87030655a677b0a4d6317bfe3a6a7d10546 (diff) | |
| download | postgresql-e40f3c7472036f5a06897a11ac79fd26ec2ccf7d.tar.gz postgresql-e40f3c7472036f5a06897a11ac79fd26ec2ccf7d.zip | |
ANALYZE a_star and its children to avoid plan instability in tests.
We've noted certain EXPLAIN queries on these tables occasionally showing
unexpected plan choices. This seems to happen because VACUUM sometimes
fails to update relpages/reltuples for one of these single-page tables,
due to bgwriter or checkpointer holding a pin on the lone page at just
the wrong time. To ensure those values get set, insert explicit ANALYZE
operations on these tables after we finish populating them. This
doesn't seem to affect any other test cases, so it's a usable fix.
Back-patch to v12. In principle the issue exists further back, but
we have not seen it before v12, so I won't risk back-patching further.
Discussion: https://postgr.es/m/24480.1569518042@sss.pgh.pa.us
Diffstat (limited to 'src/include/executor')
0 files changed, 0 insertions, 0 deletions