Re: tablecmds: reject CLUSTER ON for partitioned tables earlier - Mailing list pgsql-hackers

From Zsolt Parragi
Subject Re: tablecmds: reject CLUSTER ON for partitioned tables earlier
Date
Msg-id CAN4CZFOPSa714weVjrwSTJXHNPNrO=1v8Mf3tH5351d==9K6wg@mail.gmail.com
Whole thread Raw
In response to Re: tablecmds: reject CLUSTER ON for partitioned tables earlier  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
> can the previous error path in
> mark_index_clustered() be reached through a different mean than ALTER
> TABLE?

That was one of the things we discussed in the previous emails. The
remaining callers of that function are VACUUM FULL and CLUSTER. It
definitely can't be hit by VACUUM (it passes an InvalidOid for an
index), but CLUSTER is a bit more difficult to follow. It seems like
to me that it shouldn't be hit (CLUSTER only calls it for leaf
partitions, where the check will be false), but I'm not 100% sure
about my diagnosis.



pgsql-hackers by date:

Previous
From: Jim Jones
Date:
Subject: Re: display hot standby state in psql prompt
Next
From: Amit Kapila
Date:
Subject: Re: Newly created replication slot may be invalidated by checkpoint