[prev in list] [next in list] [prev in thread] [next in thread]
List: pgsql-bugs
Subject: Re: create partitioned table with (like table INCLUDING ALL ) fails with "insufficient columns in UN
From: Amit Langote <Langote_Amit_f8 () lab ! ntt ! co ! jp>
Date: 2018-12-14 0:42:09
Message-ID: f97f9840-1e30-32be-632d-934388436878 () lab ! ntt ! co ! jp
[Download RAW message or body]
Hi,
On 2018/12/14 8:35, Stuart wrote:
> Amit,
>
> Thanks for your response. So partitioning does not recognize a primary key
> constraint on the partition key as a unique constraint? Shouldn't it?
It does. When you dropped all UNIQUE constraints on the source table that
didn't contain object_id in it except PRIMARY KEY (object_id), then it did
indeed work, as seen in your first email:
> =# drop index knowledge_categoryfilepathurl_un ;
> DROP INDEX
>
> =# \d+ knowledge
[ ... ]
> Indexes:
> "knowledge_pk" PRIMARY KEY, btree (object_id), tablespace "pgindex"
> Inherits: products
>
> =# create table knowledge_new (like knowledge INCLUDING ALL ) PARTITION
> BY RANGE ( object_id ) ;
> CREATE TABLE
Thanks,
Amit
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic