Postgres Pro
Downloads
Home   >   mailing lists

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 29672d7c-7000-2467-a99b-33a9a79d55ea@enterprisedb.com
Whole thread Raw
In response to Re: Dump/Restore of non-default PKs  (Simon Riggs <simon.riggs@enterprisedb.com>)
Responses Re: Dump/Restore of non-default PKs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On 21.04.22 13:43, Simon Riggs wrote:
>> 1. create the table without primary key
>> 2. create the index
>> 3. attach the index as primary key constraint
>>
>> That doesn't sound attractive.
> Can you explain what you find unattractive about it?

Well, if I want to create a table with a primary key, the established 
way is to say "primary key", not to have to assemble it from multiple 
pieces.

I think this case is very similar to exclusion constraints, which also 
have syntax to specify the index access method.

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: pg_walcleaner - new tool to detect, archive and delete the unneeded wal files (was Re: pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary)
Next
From: Bharath Rupireddy
Date:
Subject: Re: pg_receivewal fail to streams when the partial file to write is not fully initialized present in the wal receiver directory