Re: ANALYZE ONLY - Mailing list pgsql-hackers

From jian he
Subject Re: ANALYZE ONLY
Date
Msg-id CACJufxHY9nOecqeJr8WsrvtHG+8BTOOXqpM7E4OuCCEcrBC7qg@mail.gmail.com
Whole thread Raw
In response to Re: ANALYZE ONLY  (Melih Mutlu <m.melihmutlu@gmail.com>)
List pgsql-hackers
On Thu, Aug 29, 2024 at 7:31 PM Melih Mutlu <m.melihmutlu@gmail.com> wrote:
>
> Hi Michael,
>
> Michael Harris <harmic@gmail.com>, 23 Ağu 2024 Cum, 13:01 tarihinde şunu yazdı:
>>
>> V2 of the patch is attached.
>
>
> Thanks for updating the patch. I have a few more minor feedbacks.
>
>> -ANALYZE [ ( <replaceable class="parameter">option</replaceable> [, ...] ) ] [ <replaceable
class="parameter">table_and_columns</replaceable>[, ...] ] 
>> +ANALYZE [ ( <replaceable class="parameter">option</replaceable> [, ...] ) ] [ [ ONLY ] <replaceable
class="parameter">table_and_columns</replaceable>[, ...] ] 
>
>
> I believe moving "[ ONLY ]" to the definitions of table_and_columns below, as you did with "[ * ]", might be better
tobe consistent with other places (see [1]) 
>
>> + if ((options & VACOPT_VACUUM) && is_partitioned_table && ! include_children)
>
>

I think you are right.

ANALYZE [ ( option [, ...] ) ] [ [ ONLY ] table_and_columns [, ...] ]

seems not explain commands like:

ANALYZE ONLY only_parted(a), ONLY only_parted(b);



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: consider -Wmissing-variable-declarations
Next
From: shveta malik
Date:
Subject: Re: Collect statistics about conflicts in logical replication