Re: Patch: Global Unique Index - Mailing list pgsql-hackers

From Thomas Kellerer
Subject Re: Patch: Global Unique Index
Date
Msg-id 6cdcb7b1-2567-1373-79d1-96467a9b305b@gmx.net
Whole thread Raw
In response to Re: Patch: Global Unique Index  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Patch: Global Unique Index
List pgsql-hackers
Tom Lane schrieb am 18.11.2022 um 16:06:
>> Do we need new syntax actually? I think that a global unique index
>> can be created automatically instead of raising an error "unique
>> constraint on partitioned table must include all partitioning
>> columns"
>
> I'm not convinced that we want this feature at all: as far as I can
> see, it will completely destroy the benefits of making a partitioned
> table in the first place.  But if we do want it, I don't think it
> should be so easy to create a global index by accident as that syntax
> approach would make it.  I think there needs to be a pretty clear YES
> I WANT TO SHOOT MYSELF IN THE FOOT clause in the command.

There are many Oracle users that find global indexes useful despite
their disadvantages.

I have seen this mostly when the goal was to get the benefits of
partition pruning at runtime which turned the full table scan (=Seq Scan)
on huge tables to partition scans on much smaller partitions.
Partition wise joins were also helpful for query performance.
The substantially slower drop partition performance was accepted in thos cases

I think it would be nice to have the option in Postgres as well.

I do agree however, that the global index should not be created automatically.

Something like CREATE GLOBAL [UNIQUE] INDEX ... would be a lot better


Just my 0.05€



pgsql-hackers by date:

Previous
From: Cary Huang
Date:
Subject: Re: Patch: Global Unique Index
Next
From: Peter Geoghegan
Date:
Subject: Re: New strategies for freezing, advancing relfrozenxid early