config

contrib

adminpack

amcheck

auth_delay

auto_explain

bloom

btree_gin

btree_gist

citext

cube

dblink

dict_int

dict_xsyn

earthdistance

file_fdw

fuzzystrmatch

hstore

hstore_plperl

hstore_plpython

intagg

intarray

isn

jsonb_plperl

jsonb_plpython

lo

ltree

ltree_plpython

oid2name

pageinspect

passwordcheck

pg_buffercache

pg_freespacemap

pg_prewarm

pg_standby

pg_stat_statements

pg_trgm

pg_visibility

expected

sql

pg_visibility.sql

.gitignore

Makefile

pg_visibility--1.0--1.1.sql

pg_visibility--1.1--1.2.sql

pg_visibility--1.1.sql

pg_visibility.c

pg_visibility.control

pgcrypto

pgrowlocks

pgstattuple

postgres_fdw

seg

sepgsql

spi

sslinfo

start-scripts

tablefunc

tcn

test_decoding

tsm_system_rows

tsm_system_time

unaccent

uuid-ossp

vacuumlo

xml2

Makefile

README

contrib-global.mk

doc

src

.dir-locals.el

.gitattributes

.gitignore

COPYRIGHT

GNUmakefile.in

HISTORY

Makefile

README

README.git

aclocal.m4

configure

configure.in

Tom Lane 6a97ca3128 Disable vacuum page skipping in selected test cases. ...

By default VACUUM will skip pages that it can't immediately get
exclusive access to, which means that even activities as harmless
and unpredictable as checkpoint buffer writes might prevent a page
from being processed.  Ordinarily this is no big deal, but we have
a small number of test cases that examine the results of VACUUM's
processing and therefore will fail if the page of interest is skipped.
This seems to be the explanation for some rare buildfarm failures.
To fix, add the DISABLE_PAGE_SKIPPING option to the VACUUM commands
in tests where this could be an issue.

In passing, remove a duplicated query in pageinspect/sql/page.sql.

Back-patch as necessary (some of these cases are as old as v10).

Discussion: https://postgr.es/m/413923.1611006484@sss.pgh.pa.us

2021-01-20 11:49:29 -05:00

..

pg_visibility.sql

Disable vacuum page skipping in selected test cases.

2021-01-20 11:49:29 -05:00