Re: Modest proposal to extend TableAM API for controlling cluster commands - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: Modest proposal to extend TableAM API for controlling cluster commands
Date
Msg-id 0900A2D2-ABB6-4F26-B167-5E6629789951@enterprisedb.com
Whole thread Raw
In response to Re: Modest proposal to extend TableAM API for controlling cluster commands  (Andres Freund <andres@anarazel.de>)
Responses Re: Modest proposal to extend TableAM API for controlling cluster commands  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers

> On Jun 15, 2022, at 6:55 PM, Andres Freund <andres@anarazel.de> wrote:
>
> I think nothing would happen in this case - only pre-clustered tables get
> clustered in an argumentless CLUSTER. What am I missing?

The "VACUUM FULL" synonym of "CLUSTER" doesn't depend on whether the target is pre-clustered, and both will run against
thetable if the user has run an ALTER TABLE..CLUSTER ON.  Now, we could try to catch that latter command with a utility
hook,but since the VACUUM FULL is still problematic, it seems cleaner to just add the callback I am proposing. 

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company






pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Modest proposal to extend TableAM API for controlling cluster commands
Next
From: Andres Freund
Date:
Subject: Re: Modest proposal to extend TableAM API for controlling cluster commands