aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistutil.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-06-24 15:02:13 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2021-06-24 15:02:13 -0400
commit802177090992511c610804da54a4603d4f50c594 (patch)
tree3762dc6ca0182677d21fb311cbb3e206835ec5b7 /src/backend/access/gist/gistutil.c
parent9b8ed0f52bffceaccf6fa650ffe482e7da20fbf2 (diff)
downloadpostgresql-802177090992511c610804da54a4603d4f50c594.tar.gz
postgresql-802177090992511c610804da54a4603d4f50c594.zip
Further stabilize postgres_fdw test.
The queries involving ft1_nopw don't stably return the same row anymore. I surmise that an autovacuum hitting "S 1"."T 1" right after the updates introduced by f61db909d/5843659d0 freed some space, changing where subsequent insertions get stored. It's only by good luck that these results were stable before, though, since a LIMIT without ORDER BY isn't well defined, and it's not like we've ever treated that table as append-only in this test script. Since we only really care whether these commands succeed or not, just replace "SELECT *" with "SELECT 1". Report: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2021-06-23%2019%3A52%3A08
Diffstat (limited to 'src/backend/access/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions