| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Peter Geoghegan <pg(at)bowt(dot)ie>, David Rowley <dgrowley(at)gmail(dot)com> |
| Subject: | Re: Trigger more frequent autovacuums of heavy insert tables |
| Date: | 2025-02-07 21:05:09 |
| Message-ID: | Z6Z1hTJahF-zYjIh@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 07, 2025 at 03:57:49PM -0500, Melanie Plageman wrote:
> As for relallfrozen, one of the justifications for adding it to
> pg_class is actually for the visibility it would provide. We have no
> way of knowing how many all-visible but not all-frozen pages there are
> on users' systems without pg_visibility. If users had this
> information, they could potentially tune their freeze-related settings
> more aggressively. Regularly reading the whole visibility map with
> pg_visibilitymap_summary() is pretty hard to justify on most
> production systems. But querying pg_class every 10 minutes or
> something is much more reasonable.
If we need it anyway, then I have no objections to using a freeze-related
metric for a freeze-related feature.
Okay, I'll actually look at the patches next...
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ilia Evdokimov | 2025-02-07 21:28:28 | Re: explain analyze rows=%.0f |
| Previous Message | Matheus Alcantara | 2025-02-07 21:01:36 | Re: explain analyze rows=%.0f |