Re: ANALYZE ONLY - Mailing list pgsql-hackers

From Robert Haas
Subject Re: ANALYZE ONLY
Date
Msg-id CA+TgmobJeWN8rPEPz9t33zWDd5AztxFTvheDFAjUxAdT4Y1ODg@mail.gmail.com
Whole thread Raw
In response to Re: ANALYZE ONLY  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-hackers
On Tue, Aug 20, 2024 at 6:53 PM David Rowley <dgrowleyml@gmail.com> wrote:
> On Wed, 21 Aug 2024 at 06:41, Robert Haas <robertmhaas@gmail.com> wrote:
> > I like trying to use ONLY somehow.
>
> Do you mean as an ANALYZE command option, i.e. ANALYZE (only) table;
> or as a table modifier like gram.y's extended_relation_expr?

The table modifier idea seems nice to me.

> If we did it as a per-table option, then we'd need to consider what
> should happen if someone did: "VACUUM ONLY parttab;". Probably
> silently doing nothing wouldn't be good. Maybe a warning, akin to
> what's done in:
>
> postgres=# analyze (skip_locked) a;
> WARNING:  skipping analyze of "a" --- lock not available

Perhaps. I'm not sure about this part.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: px shi
Date:
Subject: Re: [Bug Fix]standby may crash when switching-over in certain special cases
Next
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Conflict detection and logging in logical replication