Re: Dump/Restore of non-default PKs - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Dump/Restore of non-default PKs
Date
Msg-id c4baf6b6-f60a-8c74-8ed4-b43fcf4f4b1c@enterprisedb.com
Whole thread Raw
In response to Re: Dump/Restore of non-default PKs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Dump/Restore of non-default PKs  (Simon Riggs <simon.riggs@enterprisedb.com>)
List pgsql-hackers
On 22.04.22 16:14, Tom Lane wrote:
> That analogy would be compelling if exclusion constraints were a
> SQL-standard feature; but they aren't so their clause syntax is
> fully under our control.  The scenario that worries me is that
> somewhere down the pike, the SQL committee might extend the
> syntax of PKEY/UNIQUE constraint clauses in a way that breaks
> our nonstandard extensions of them.

Some syntax like

     PRIMARY KEY (x, y) USING ACCESS METHOD hash

should be able to avoid any future clashes.



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: json_query - redundant result
Next
From: Andrew Dunstan
Date:
Subject: Re: json_query - redundant result