On Thu, 2022-12-15 at 17:19 -0800, Nathan Bossart wrote: > The attached patch adds WARNING messages, but we're still far from > consistency with VACUUM/ANALYZE.
But why make CLUSTER more like VACUUM? Shouldn't we make VACUUM/CLUSTER/ANALYZE more like INSERT/SELECT/REINDEX? As far as I can tell, the only way you can get in this situation in 15 is by having a superuser create partitions in a non-superuser's table. I don't think that was an intended use case, so it's probably just historical reasons that VACUUM/CLUSTER/ANALYZE ended up that way, not precedent we should necessarily follow. -- Jeff Davis PostgreSQL Contributor Team - AWS
