| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | "Karthik Jagadish (kjagadis)" <kjagadis(at)cisco(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, "Prasanna Satyanarayanan (prassaty)" <prassaty(at)cisco(dot)com>, "Chandruganth Ayyavoo Selvam (chaayyav)" <chaayyav(at)cisco(dot)com> |
| Subject: | Re: Vacuumdb --force-index-cleanup option not available in postgres 12.9 |
| Date: | 2022-11-15 15:32:32 |
| Message-ID: | 20221115153231.GY26337@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 15, 2022 at 02:45:37PM +0000, Karthik Jagadish (kjagadis) wrote:
> Hi,
>
> In the postgres document we notice that the --force-index-cleanup option is available in PostgreSQL server 12 and Later. We have postgres db running on 12.9 but we don’t see this option.
>
> https://www.postgresql.org/docs/current/app-vacuumdb.html
Those are the docs for the current version (v15).
vacuumdb is a client, which can run against older (or newer) servers.
The --force-index-cleanup option was added in v14, and can be used
against servers back to v12. But the command-line option to the
vacuumdb client doesn't exist before v14 (even though the server-side
supports it).
> Also we notice that vacuum is happening at regular intervals but the
> space occupied by indexes is always increasing.
I don't know. But this busy mailing list is for development; these
questions would be better addressed to pgsql-user.
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karthik Jagadish (kjagadis) | 2022-11-15 15:38:47 | Index not getting cleaned even though vacuum is running |
| Previous Message | Peter Eisentraut | 2022-11-15 14:58:57 | Re: dynamic result sets support in extended query protocol |