| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | wenhui qiu <qiuwenhuifx(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Do we reduce autovacuum_naptime max values |
| Date: | 2026-09-11 07:59:37 |
| Message-ID: | AAC022FE-C5A0-4776-8CEC-BC277830A97F@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 9 Sep 2026, at 11:49, wenhui qiu <qiuwenhuifx(at)gmail(dot)com> wrote:
> I’ve heard through various channels that `autovacuum_naptime` was mistakenly
> set to 23 hours, resulting in an XID wraparound incident. Maybe the max value
> of more than 1 hour is too large ,so can we reduce the max value to 3600? Of
> course, an inappropriate XID request is also a contributing factor to the
> incident.We believe a reasonable range should be set for this maximum value.
The current range 1..INT_MAX/1000 is indeed pretty wide, but I think it's hard,
or even impossible, to conclude that no one would ever want more than X. Could
the documentation be improved perhaps?
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2026-09-11 08:03:08 | Re: Review items for EXCEPT TABLE publication |
| Previous Message | Peter Smith | 2026-09-11 07:55:41 | Re: PSQL schema "describe" \dn is not escaping quotes |