Re: Patch: Global Unique Index
Ilya Anfimov <ilan@tzirechnoy.com>
From: Ilya Anfimov <ilan@tzirechnoy.com>
To: pgsql-hackers@lists.postgresql.org
Date: 2022-11-29T12:38:41Z
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 →
-
Apply a better fix to mdunlinkfork().
- 85d8b30724c0 16.0 cited
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.