diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2015-05-26 14:10:46 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2015-05-26 14:11:12 -0400 |
commit | 1f303fd1be51f26553e7c95d8696aa4e28ece1c6 (patch) | |
tree | 93f1b3633727db931f79fd9ba224c81dc9540b74 /src/backend/utils/adt/jsonfuncs.c | |
parent | fba12c8c6c4159e1923958a4006b26f3cf873254 (diff) | |
download | postgresql-1f303fd1be51f26553e7c95d8696aa4e28ece1c6.tar.gz postgresql-1f303fd1be51f26553e7c95d8696aa4e28ece1c6.zip |
Suppress occasional failures in brin regression test.
brin.sql included a call of brin_summarize_new_values(), and expected
it to always report exactly 5 summarization events. This failed sometimes
during parallel regression tests, as a consequence of the database-wide
VACUUM in gist.sql getting there first. The most future-proof way
to avoid variation in the test results is to forget about using
brin_summarize_new_values() and just do a plain "VACUUM brintest",
which will exercise the same code anyway.
Having done that, there's no need for preventing autovacuum on brintest;
doing so just reduces the scope of test coverage, so let's not.
Diffstat (limited to 'src/backend/utils/adt/jsonfuncs.c')
0 files changed, 0 insertions, 0 deletions