From: | Ilya Anfimov <ilan(at)tzirechnoy(dot)com> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Patch: Global Unique Index |
Date: | 2022-11-29 12:38:41 |
Message-ID: | Y4X9UWO920xMyv5Q@azor.tzirechnoy.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 18, 2022 at 12:03:53PM +0300, Sergei Kornilov wrote:
> Hello
> 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 may suggest even more of the new syntax.
If someone has to implement sequential index checking on unique
constraints, then it would be useful to be able to do that inde-
pendent of partitioning also.
E.g. for some kinds of manual partitions or for strangely de-
signed datasets. Or for some of the table partitions instead for
all of them.
For that reason, perhaps some other type of unique index -- that
is not an index per se, but a check against a set of indexes --
could be added. Or, perhaps, not an index, but an EXCLUDE con-
straint of that kind.
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2022-11-29 12:45:58 | Re: GUC for temporarily disabling event triggers |
Previous Message | Amit Kapila | 2022-11-29 12:33:53 | Re: Perform streaming logical transactions by background workers and parallel apply |