Re: partitioning and identity column - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: partitioning and identity column
Date
Msg-id c05e2ff9-4d65-4f8e-b233-d146ac12ccd2@eisentraut.org
Whole thread Raw
In response to Re: partitioning and identity column  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
Responses Re: partitioning and identity column
List pgsql-hackers
On 22.01.24 13:23, Ashutosh Bapat wrote:
>>       if (newdef->identity)
>>       {
>>           Assert(!is_partioning);
>>           /*
>>            * Identity is never inherited.  The new column can have an
>>            * identity definition, so we always just take that one.
>>            */
>>           def->identity = newdef->identity;
>>       }
>>
>> Thoughts?
> 
> That code block already has Assert(!is_partition) at line 3085. I
> thought that Assert is enough.

Ok.  Maybe just rephrase that comment somehow then?

> There's another thing I found. The file isn't using
> check_stack_depth() in the function which traverse inheritance
> hierarchies. This isn't just a problem of the identity related
> function but most of the functions in that file. Do you think it's
> worth fixing it?

I suppose the number of inheritance levels is usually not a problem for 
stack depth?




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Built-in CTYPE provider
Next
From: Heikki Linnakangas
Date:
Subject: Re: Adding facility for injection points (or probe points?) for more advanced tests