Re: partitioning and identity column
Alexander Law <exclusion@gmail.com>
From: Alexander Lakhin <exclusion@gmail.com>
To: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-04-28T06:59:44Z
Lists: pgsql-hackers
27.04.2024 18:00, Alexander Lakhin wrote: > > Please look also at another script, which produces the same error: I've discovered yet another problematic case: CREATE TABLE tbl1 (a int GENERATED ALWAYS AS IDENTITY, b text) PARTITION BY LIST (a); CREATE TABLE tbl2 (b text, a int NOT NULL); ALTER TABLE tbl1 ATTACH PARTITION tbl2 DEFAULT; INSERT INTO tbl2 DEFAULT VALUES; ERROR: no owned sequence found Though it works with tbl2(a int NOT NULL, b text)... Take a look at this too, please. Best regards, Alexander
Commits
-
Fix assorted bugs related to identity column in partitioned tables
- 509199587df7 17.0 landed
-
Remove extra check_stack_depth() from dropconstraint_internal()
- 75bcba6cbd2a 17.0 landed
-
Support identity columns in partitioned tables
- 699586315704 17.0 landed
-
doc: Add Identity Column section under Data Definition chapter
- a37bb7c13995 17.0 landed
-
Assert that partition inherits from only one parent in MergeAttributes()
- d22d98c34171 17.0 landed
-
doc: Decorate PostgreSQL with productname tag
- 58b20e6d75e5 17.0 landed
-
Fix prologue of get_partition_ancestors()
- e557db106ef6 17.0 landed