Re: ERROR: insufficient columns in the PRIMARY KEY constraint definition

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

Noted, thank you all. 
On Tuesday, September 29, 2020, 05:12:40 PM PDT, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:

On Wed, 30 Sep 2020 at 13:06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > Here's the proposed error message fix, using the wording that saves
> > $1.99.  I agree that trying to cram the constraint type in the primary
> > message is uglier.
>
> WFM.

Looks good to me too.

David

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2020-09-30 01:02:52 Re: table partition with inheritance having current_timestamp issue if we miss range table
Previous Message Nagaraj Raj 2020-09-30 00:45:16 Trigger function is not working as expected after migration from v9.6 to v11.7