[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-hackers
Subject:    Re: Dump/Restore of non-default PKs
From:       Peter Eisentraut <peter.eisentraut () enterprisedb ! com>
Date:       2022-04-28 14:09:18
Message-ID: c4baf6b6-f60a-8c74-8ed4-b43fcf4f4b1c () enterprisedb ! com
[Download RAW message or body]

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.


[prev in list] [next in list] [prev in thread] [next in thread]