Re: [EXTERNAL] Re: ERROR: insufficient columns in the PRIMARY KEY constraint definition

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Godfrin, Philippe E" <Philippe(dot)Godfrin(at)nov(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, Nagaraj Raj <nagaraj(dot)sf(at)yahoo(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: [EXTERNAL] Re: ERROR: insufficient columns in the PRIMARY KEY constraint definition
Date: 2020-09-30 14:16:33
Message-ID: 840317.1601475393@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Godfrin, Philippe E" <Philippe(dot)Godfrin(at)nov(dot)com> writes:
> I am curious why this is considered Class 0A, versus 42 (syntax error?)

FEATURE_NOT_SUPPORTED seems perfectly appropriate from here.
What you tried to do is not semantically nonsensical, it's just something
we can't do given the current architecture for partitioned tables.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-09-30 14:35:55 BUG #16648: Using postgres:12.4-alpine docker image, get 12.2 when running postgres -V command inside container
Previous Message Godfrin, Philippe E 2020-09-30 13:31:35 RE: [EXTERNAL] Re: ERROR: insufficient columns in the PRIMARY KEY constraint definition