aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/functions.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-08-11 18:55:32 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2019-08-11 18:55:32 -0400
commitb43f7c117e667fb51df36ca62e6c86054b0f8d03 (patch)
tree0da7950558eccd6ae1067eee44bb163c0d043a41 /src/backend/executor/functions.c
parentd54ceb9e176152f930e60709e07c636e8e5414f5 (diff)
downloadpostgresql-b43f7c117e667fb51df36ca62e6c86054b0f8d03.tar.gz
postgresql-b43f7c117e667fb51df36ca62e6c86054b0f8d03.zip
Partially revert "Insert temporary debugging output in regression tests."
This reverts much of commit f03a9ca4366d064d89b7cf7ed75d4e43f2ed0667, but leaves the relpages/reltuples probe in select_parallel.sql. The pg_stat_all_tables probes are unstable enough to be annoying, and it no longer seems likely that they will teach us anything more about the underlying problem. I'd still like some more confirmation though that the observed plan instability is caused by VACUUM leaving relpages/reltuples as zero for one of these tables. Discussion: https://postgr.es/m/CA+hUKG+0CxrKRWRMf5ymN3gm+BECHna2B-q1w8onKBep4HasUw@mail.gmail.com
Diffstat (limited to 'src/backend/executor/functions.c')
0 files changed, 0 insertions, 0 deletions