| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Ian Lawrence Barwick <barwick(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Anastasia Lubennikova <lubennikovaav(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Subject: | Re: Testing autovacuum wraparound (including failsafe) |
| Date: | 2023-07-12 11:47:51 |
| Message-ID: | C9CF2F76-0D81-4C9D-9832-202BE8517056@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 12 Jul 2023, at 09:52, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> 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.
+# bump the query timeout to avoid false negatives on slow test syetems.
typo: s/syetems/systems/
+# bump the query timeout to avoid false negatives on slow test syetems.
+$ENV{PG_TEST_TIMEOUT_DEFAULT} = 600;
Does this actually work? Utils.pm read the environment variable at compile
time in the BEGIN block so this setting won't be seen? A quick testprogram
seems to confirm this but I might be missing something.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2023-07-12 11:48:56 | Re: Synchronizing slots from primary to standby |
| Previous Message | Peter Eisentraut | 2023-07-12 11:34:56 | Re: Consistent coding for the naming of LR workers |