pgsql: Remove undocumented restriction against duplicate partitionkey - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Remove undocumented restriction against duplicate partitionkey
Date
Msg-id E1fgEoL-0006Yl-9D@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Remove undocumented restriction against duplicate partition key columns.

transformPartitionSpec rejected duplicate simple partition columns
(e.g., "PARTITION BY RANGE (x,x)") but paid no attention to expression
columns, resulting in inconsistent behavior.  Worse, cases like
"PARTITION BY RANGE (x,(x))") were accepted but would then result in
dump/reload failures, since the expression (x) would get simplified
to a plain column later.

There seems no better reason for this restriction than there was for
the one against duplicate included index columns (cf commit 701fd0bbc),
so let's just remove it.

Back-patch to v10 where this code was added.

Report and patch by Yugo Nagata.

Discussion: https://postgr.es/m/20180712165939.36b12aff.nagata@sraoss.co.jp

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/24097167558bafbc1ea32f67ea5840e5650ad4e7

Modified Files
--------------
src/backend/commands/tablecmds.c           | 15 ---------------
src/test/regress/expected/create_table.out |  5 -----
src/test/regress/sql/create_table.sql      |  5 -----
3 files changed, 25 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix pg_get_indexdef()'s behavior for included index columns.
Next
From: Alexander Korotkov
Date:
Subject: pgsql: Fix handling of empty uncompressed posting list pages in GIN