Re: Patch: Global Unique Index
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Sergei Kornilov <sk@zsrv.org>, Cary Huang <cary.huang@highgo.ca>, Pgsql Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-11-18T15:14:44Z
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
pá 18. 11. 2022 v 16:06 odesílatel Tom Lane <tgl@sss.pgh.pa.us> napsal: > Sergei Kornilov <sk@zsrv.org> writes: > > 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. > isn't possible to have a partitioned index? https://www.highgo.ca/2022/10/14/global-index-a-different-approach/ Regards Pavel > > regards, tom lane > > >