| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Michael Harris <harmic(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ANALYZE ONLY |
| Date: | 2024-08-20 18:40:41 |
| Message-ID: | CA+Tgmob=UV9SVqhD0Jj3qRcVNEymi=qQ0ywP_XQKC4c_K1CqBw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 20, 2024 at 1:52 AM Michael Harris <harmic(at)gmail(dot)com> wrote:
> 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.
I like trying to use ONLY somehow.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2024-08-20 18:41:18 | Re: Partial aggregates pushdown |
| Previous Message | Alvaro Herrera | 2024-08-20 18:37:34 | Re: MultiXact\SLRU buffers configuration |