Re: Testing autovacuum wraparound (including failsafe) - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: Testing autovacuum wraparound (including failsafe)
Date
Msg-id CAD21AoCmwfbpmiLk3qtD06osv_NKjmJpeoGNhCN1C3-0HFPBfA@mail.gmail.com
Whole thread Raw
In response to Re: Testing autovacuum wraparound (including failsafe)  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Testing autovacuum wraparound (including failsafe)
List pgsql-hackers
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

Attachment

pgsql-hackers by date:

Previous
From: Gurjeet Singh
Date:
Subject: Better help output for pgbench -I init_steps
Next
From: Masahiro Ikeda
Date:
Subject: Re: Support to define custom wait events for extensions