Re: partitioning and identity column
От | Peter Eisentraut |
---|---|
Тема | Re: partitioning and identity column |
Дата | |
Msg-id | 2f110378-f20e-419b-bc76-98058536a223@eisentraut.org обсуждение исходный текст |
Ответ на | Re: partitioning and identity column (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>) |
Ответы |
Re: partitioning and identity column
|
Список | pgsql-hackers |
On 17.01.24 06:36, Ashutosh Bapat wrote: > On Wed, Jan 17, 2024 at 12:30 AM Peter Eisentraut <peter@eisentraut.org> wrote: >> >> On 09.01.24 15:10, Ashutosh Bapat wrote: >>> Here's complete patch-set. >> >> Looks good! Committed. >> > > Thanks a lot Peter. I found another piece of code that might need updating, or at least the comment. In MergeAttributes(), in the part that merges the specified column definitions into the inherited ones, it says /* * Identity is never inherited. The new column can have an * identity definition, so we always just take that one. */ def->identity = newdef->identity; This is still correct for regular inheritance, but not for partitioning. I think for partitioning, this is not reachable because you can't specify identity information when you create a partition(?). So maybe something like 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?
В списке pgsql-hackers по дате отправления: