aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuildbuffers.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-04-02 19:43:48 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-04-02 19:43:51 -0400
commit7cb0a423f914af6936d13a8c7f2e35c0a4e4bd14 (patch)
tree51402e2660d6384cd08135956989ed7b0bac0dd6 /src/backend/access/gist/gistbuildbuffers.c
parent8da1538b39f2803fdc75de8505dd096e29e65a52 (diff)
downloadpostgresql-7cb0a423f914af6936d13a8c7f2e35c0a4e4bd14.tar.gz
postgresql-7cb0a423f914af6936d13a8c7f2e35c0a4e4bd14.zip
Improve stability fix for partition_aggregate test.
Instead of disabling autovacuum on these test tables, adjust the partition boundaries so that the child partitions are not all the same size. That should cause the planner to use a predictable ordering of the per-partition scan nodes even in cases where autovacuum causes the rowcount estimates to be off a bit. Moreover, this also lets these tests show that the planner does properly order the tables in descending size order, something that wasn't being proven before. The pagg_tab1 and pagg_tab2 partitions are still all the same size, but that should be fine, because those tables are so small that (1) autovacuum won't fire on them, and (2) even if it did, it couldn't change the reltuples value --- with only one page, it can't see just part of the relation. Discussion: https://postgr.es/m/24467.1585838693@sss.pgh.pa.us
Diffstat (limited to 'src/backend/access/gist/gistbuildbuffers.c')
0 files changed, 0 insertions, 0 deletions