Re: ANALYZE ONLY - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: ANALYZE ONLY
Date
Msg-id CAGECzQTq_OPhXvA+VK3zzQ-ZYa97Bg8D+JomjXTuiTs9P6Q4Tw@mail.gmail.com
Whole thread Raw
In response to ANALYZE ONLY  (Michael Harris <harmic@gmail.com>)
Responses Re: ANALYZE ONLY
List pgsql-hackers
On Tue, 20 Aug 2024 at 07:52, Michael Harris <harmic@gmail.com> wrote:
>   1. Would such a feature be welcomed? Are there any traps I might not
> have thought of?

I think this sounds like a reasonable feature.


>   2. The existing ANALYZE command has the following structure:
>
>      ANALYZE [ ( option [, ...] ) ] [ table_and_columns [, ...] ]
>
>      It would be easiest to add ONLY as another option, but that
> doesn't look quite
>      right to me - surely the ONLY should be attached to the table name?
>      An alternative would be:
>
>      ANALYZE [ ( option [, ...] ) ] [ONLY] [ table_and_columns [, ...] ]
>
> Any feedback or advice would be great.

Personally I'd prefer a new option to be added. But I agree ONLY isn't
a good name then. Maybe something like SKIP_PARTITIONS.



pgsql-hackers by date:

Previous
From: Jakub Wartak
Date:
Subject: Re: Doc limitation update proposal: include out-of-line OID usage per TOAST-ed columns
Next
From: Ronan Dunklau
Date:
Subject: Re: Provide a pg_truncate_freespacemap function