Re: Patch: Global Unique Index
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: Pavel Stehule <pavel.stehule@gmail.com>, Dilip Kumar <dilipbalaut@gmail.com>
Cc: Thomas Kellerer <shammat@gmx.net>, pgsql-hackers@lists.postgresql.org, Cary Huang <cary.huang@highgo.ca>
Date: 2022-11-24T16:09:23Z
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 Thu, Nov 24, 2022 at 07:03:24AM +0100, Pavel Stehule wrote: > I can imagine a unique index on partitions without a special mark, that > will be partitioned, That exists since v11, as long as the index keys include the partition keys. > and a second variant classic index created over a partitioned table, > that will be marked as GLOBAL. That's not what this patch is about, though. On Thu, Nov 24, 2022 at 08:52:16PM +0530, Dilip Kumar wrote: > but now you will have one gigantic index and which will be vacuumed > every time we vacuum any of the partitions. This patch isn't implemented as "one gigantic index", though. -- Justin