aboutsummaryrefslogtreecommitdiff
path: root/src/test/perl/PostgresNode.pm
diff options
context:
space:
mode:
authorPeter Geoghegan <pg@bowt.ie>2021-04-05 17:17:40 -0700
committerPeter Geoghegan <pg@bowt.ie>2021-04-05 17:17:40 -0700
commitf6b8f19a084ce949522fcbc940dc116c034cfc47 (patch)
treeb26b7a0ba27be29d969b84e54afb17a702a5ef2f /src/test/perl/PostgresNode.pm
parent09c1c6ab4bc5764dd69c53ccfd43b2060b1fd090 (diff)
downloadpostgresql-f6b8f19a084ce949522fcbc940dc116c034cfc47.tar.gz
postgresql-f6b8f19a084ce949522fcbc940dc116c034cfc47.zip
Allocate access strategy in parallel VACUUM workers.
Commit 49f49def took entirely the wrong approach to fixing this issue. Just allocate a local buffer access strategy in each individual worker instead of trying to propagate state. This state was never propagated by parallel VACUUM in the first place. It looks like the only reason that this worked following commit 40d964ec was that it involved static global variables, which are initialized to 0 per the C standard. A more comprehensive fix may be necessary, even on HEAD. This fix should at least get the buildfarm green once again. Thanks once again to Thomas Munro for continued off-list assistance with the issue.
Diffstat (limited to 'src/test/perl/PostgresNode.pm')
0 files changed, 0 insertions, 0 deletions