| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Teaching users how they can get the most out of HOT in Postgres 14 |
| Date: | 2021-06-17 12:55:32 |
| Message-ID: | 20210617125532.GC31772@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
+ <literal>AUTO</literal>. With <literal>OFF</literal> index
+ cleanup is disabled, with <literal>ON</literal> it is enabled,
OFF comma
+ bypassing index cleanup in cases where there is more than zero
+ dead tuples.
*are* more than zero
Or (preferably): "cases when there are no dead tuples at all"
+ If <literal>INDEX_CLEANUP</literal> is set to
+ <literal>OFF</literal> performance may suffer, because as the
OFF comma
+ removed until index cleanup is completed. This option has no
+ effect for tables that do not have an index and is ignored if
+ the <literal>FULL</literal> option is used.
I'd say "tables that have no indexes,"
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2021-06-17 12:57:41 | Re: Issue with some calls to GetMultiXactIdMembers() |
| Previous Message | Justin Pryzby | 2021-06-17 12:52:54 | Re: when the startup process doesn't (logging startup delays) |