| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: VACUUM (INDEX_CLEANUP OFF) and GIN indexes |
| Date: | 2023-04-25 16:42:12 |
| Message-ID: | 340387D3-197E-441B-AAB9-26B9B9656B1A@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Apr 25, 2023, at 09:35, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
> It's skipped by VACUUM, but not by ANALYZE. So if you're using the
> reloption version of index_cleanup=off, it isn't necessarily going to
> stop autovacuum/autoanalyze from doing pending list cleanup.
Ugh, thanks. I wasn't aware that it was flushed by ANALYZE as well. The current algorithm for pending list flush is kind of problematic in itself, because it relies on the highly optimistic assumption that the pending list won't grow very much while the list is being flushed.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter J. Holzer | 2023-04-25 20:02:24 | Re: DBD::Pg (version 3.16.3) returns EMPTY char columns as 'undef' |
| Previous Message | Peter Geoghegan | 2023-04-25 16:35:37 | Re: VACUUM (INDEX_CLEANUP OFF) and GIN indexes |