| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Melanie Plageman <melanieplageman(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Emit fewer vacuum records by reaping removable tuples during pruning |
| Date: | 2024-01-18 15:50:13 |
| Message-ID: | CA+TgmobS=4c4DnJr09+Kg9p+fiY_GBwkJo_czRFp9kCYoygXzA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 18, 2024 at 10:42 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Now, that said, I suspect that we actually could reduce FSM_CATEGORIES
> somewhat without causing any real problems, because many tables are
> going to have tuples that are all about the same size, and even in a
> table where the sizes vary more than is typical, a single tuple can't
> consume more than a quarter of the page,
Actually, I think that's a soft limit, not a hard limit. But the
granularity above that level probably doesn't need to be very high, at
leat.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias van de Meent | 2024-01-18 15:54:06 | Re: Sequence Access Methods, round two |
| Previous Message | Peter Eisentraut | 2024-01-18 15:49:11 | Re: More new SQL/JSON item methods |