Re: Testing autovacuum wraparound (including failsafe)
Masahiko Sawada <sawada.mshk@gmail.com>
From: Masahiko Sawada <sawada.mshk@gmail.com>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: John Naylor <john.naylor@enterprisedb.com>,
Heikki Linnakangas <hlinnaka@iki.fi>, Ian Lawrence Barwick <barwick@gmail.com>, Andres Freund <andres@anarazel.de>, Anastasia Lubennikova <lubennikovaav@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Peter Geoghegan <pg@bowt.ie>
Date: 2023-07-12T07:52:23Z
Lists: pgsql-hackers
Attachments
- v4-0001-Add-tests-for-XID-wraparound.patch (application/octet-stream) patch v4-0001
On Thu, Apr 27, 2023 at 11:12 PM Daniel Gustafsson <daniel@yesql.se> wrote: > > > On 27 Apr 2023, at 16:06, Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > On Fri, Apr 21, 2023 at 12:02 PM John Naylor > > <john.naylor@enterprisedb.com> wrote: > > >> ...that call to background_psql doesn't look like other ones that have "key => value". Is there something I'm missing? > > > > Thanks for reporting. I think that the patch needs to be updated since > > commit 664d757531e1 changed background psql TAP functions. I've > > attached the updated patch. > > Is there a risk that the background psql will time out on slow systems during > the consumption of 2B xid's? Since you mainly want to hold it open for the > duration of testing you might want to bump it to avoid false negatives on slow > test systems. Agreed. The timeout can be set by manually setting PG_TEST_TIMEOUT_DEFAULT, but I bump it to 10 min by default. And it now require setting PG_TET_EXTRA to run it. Regards, -- Masahiko Sawada Amazon Web Services: https://aws.amazon.com
Commits
-
Fix meson installation of xid_wraparound test.
- 1aa67a5ea687 17.0 landed
-
Add tests for XID wraparound.
- e255b646a16b 17.0 landed
-
Add option to specify timeout seconds to BackgroundPsql.pm.
- 334f512f45eb 17.0 landed
-
Fix wrong description of BackgroundPsql's timeout.
- 2d758dca1b31 16.2 landed
- 5abff2aaa1ab 17.0 landed
-
Refactor background psql TAP functions
- 664d757531e1 16.0 cited
-
Consider triggering VACUUM failsafe during scan.
- c242baa4a831 14.0 landed
-
Fix autovacuum log output heap truncation issue.
- fbe9b80610fe 14.0 landed