Alvaro Herrera writes:
> On 2019-Apr-21, Tom Lane wrote:
>> ISTM that this is a bug, not a feature: if there's any point at
>> all to saying ONLY in this context, it's that we're not supposed
>> to be doing anything as expensive as adding a new constraint to
>> a child partition. No? So I think
On 2019-Apr-21, Tom Lane wrote:
> ISTM that this is a bug, not a feature: if there's any point at
> all to saying ONLY in this context, it's that we're not supposed
> to be doing anything as expensive as adding a new constraint to
> a child partition. No? So I think that this should have failed.
While fooling around with the patch shown at
<12166.159...@sss.pgh.pa.us>, I noticed this rather strange
pre-existing behavior (tested on v11 as well as HEAD):
regression=# create table idxpart (a int) partition by range (a);
CREATE TABLE
regression=# create table idxpart0 (like idxpart);
CREA
