| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com> |
| Subject: | Re: New IndexAM API controlling index vacuum strategies |
| Date: | 2021-04-07 03:16:27 |
| Message-ID: | CAH2-Wzkt39MHtJoDemVJLp1d-yqmTnv_KuLMhNu2+gcWXjn7mA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 6, 2021 at 7:05 AM Matthias van de Meent
<boekewurm+postgres(at)gmail(dot)com> wrote:
> If you have updated patches, I'll try to check them this evening (CEST).
Here is v11, which is not too different from v10 as far as the
truncation stuff goes.
Masahiko should take a look at the last patch again. I renamed the
GUCs to reflect the fact that we do everything possible to advance
relfrozenxid in the case where the fail safe mechanism kicks in -- not
just skipping index vacuuming. It also incorporates your most recent
round of feedback.
Thanks
--
Peter Geoghegan
| Attachment | Content-Type | Size |
|---|---|---|
| v11-0001-Truncate-line-pointer-array-during-VACUUM.patch | application/octet-stream | 10.5 KB |
| v11-0002-Bypass-index-vacuuming-in-some-cases.patch | application/octet-stream | 28.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kazutaka Onishi | 2021-04-07 03:30:00 | Re: TRUNCATE on foreign table |
| Previous Message | yuzuko | 2021-04-07 03:13:13 | Re: Autovacuum on partitioned table (autoanalyze) |