| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Cc: | Thomas Kellerer <shammat(at)gmx(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Cary Huang <cary(dot)huang(at)highgo(dot)ca> |
| Subject: | Re: Patch: Global Unique Index |
| Date: | 2022-11-24 16:09:23 |
| Message-ID: | 20221124160923.GO11463@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | T Adachi | 2022-11-24 16:31:12 | Does pg_rman support PG15? |
| Previous Message | Takamichi Osumi (Fujitsu) | 2022-11-24 15:39:57 | RE: logical replication restrictions |