| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, 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-11-27 13:40:09 |
| Message-ID: | 1F07AA87-01CE-42F0-918C-2858D20D4844@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 27 Nov 2023, at 14:06, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> Is it true that we can modify the timeout after creating
> BackgroundPsql object? If so, it seems we don't need to introduce the
> new timeout argument. But how?
I can't remember if that's leftovers that incorrectly remains from an earlier
version of the BackgroundPsql work, or if it's a very bad explanation of
->set_query_timer_restart(). The timeout will use the timeout_default value
and that cannot be overridden, it can only be reset per query.
With your patch the timeout still cannot be changed, but at least set during
start which seems good enough until there are tests warranting more complexity.
The docs should be corrected to reflect this in your patch.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2023-11-27 13:41:40 | Re: logical decoding and replication of sequences, take 2 |
| Previous Message | Heikki Linnakangas | 2023-11-27 13:39:16 | Re: Optimizing nbtree ScalarArrayOp execution, allowing multi-column ordered scans, skip scan |