Re: "RETURNING PRIMARY KEY" syntax extension - Mailing list pgsql-hackers

From Vik Fearing
Subject Re: "RETURNING PRIMARY KEY" syntax extension
Date
Msg-id 53978506.3080004@dalibo.com
Whole thread Raw
In response to Re: "RETURNING PRIMARY KEY" syntax extension  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: "RETURNING PRIMARY KEY" syntax extension  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On 06/09/2014 07:13 PM, Andres Freund wrote:
> On 2014-06-09 13:42:22 +0200, Vik Fearing wrote:
>> On 06/09/2014 09:06 AM, Gavin Flower wrote:
>>> From memory all unique keys can be considered 'candidate primary keys',
>>> but only one can be designated 'the PRIMARY KEY'.
>>
>> Almost.  Candidate keys are also NOT NULL.
> 
> The list actually is a bit longer. They also cannot be partial.

What?  AFAIK, that only applies to an index.  How can the data itself be
partial?

> There's generally also the restriction that for some contexts - like
> e.g. foreign keys - primary/candidate keys may not be deferrable..

Again, what is deferrable data?
-- 
Vik



pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: Why is it "JSQuery"?
Next
From: Craig Ringer
Date:
Subject: Re: API change advice: Passing plan invalidation info from the rewriter into the planner?