Horton

Re: Patch: Global Unique Index

Vik Fearing <vik@postgresfriends.org>

View thread
From: Vik Fearing <vik@postgresfriends.org>
To: Laurenz Albe <laurenz.albe@cybertec.at>, Cary Huang <cary.huang@highgo.ca>, Thomas Kellerer <shammat@gmx.net>
Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-11-30T09:09:49Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Apply a better fix to mdunlinkfork().

On 11/29/22 17:29, Laurenz Albe wrote:
> On Tue, 2022-11-29 at 13:58 +0100, Vik Fearing wrote:
>> I disagree.  A user does not need to know that a table is partitionned,
>> and if the user wants a unique constraint on the table then making them
>> type an extra word to get it is just annoying.
> 
> Hmm.  But if I created a primary key without thinking too hard about it,
> only to discover later that dropping old partitions has become a problem,
> I would not be too happy either.

I have not looked at this patch, but my understanding of its design is 
the "global" part of the index just makes sure to check a unique index 
on each partition.  I don't see from that how dropping old partitions 
would be a problem.
-- 
Vik Fearing