Re: partitioning and identity column

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: partitioning and identity column
Date: 2024-01-22 18:59:32
Message-ID: c05e2ff9-4d65-4f8e-b233-d146ac12ccd2@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2024-01-22 19:02:48 Re: Adding facility for injection points (or probe points?) for more advanced tests
Previous Message Peter Eisentraut 2024-01-22 18:49:56 Re: Built-in CTYPE provider