| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Nikita Malakhov <hukutoc(at)gmail(dot)com>, wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Proposal: Global Index for PostgreSQL |
| Date: | 2025-06-11 03:04:24 |
| Message-ID: | CAFiTN-tzc4D9KqKRHJzWMB3QTB+KK1jKCThLCwSxa8RwcvrknQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 11, 2025 at 1:08 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> On Mon, Jun 9, 2025 at 05:51:25PM -0400, Bruce Momjian wrote:
> > On Mon, Jun 9, 2025 at 03:28:38PM +0530, Dilip Kumar wrote:
> > There are certainly use cases where this would be helpful, but I think
> > the big question is whether it would have so many negatives that most
> > people who try to use it would eventually remove it. I have heard that
> > happened to other relational systems who support global indexes, so I
> > think we have to consider that possibility. The problem is you might
> > need to actually write the patch to find out.
>
> FYI, I wrote a blog about global indexes in 2020:
Oh interesting, I would be happy to have a look at it, Thanks.
--
Regards,
Dilip Kumar
Google
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuro Yamada | 2025-06-11 03:07:44 | Re: Add enable_groupagg GUC parameter to control GroupAggregate usage |
| Previous Message | Dilip Kumar | 2025-06-11 03:03:33 | Re: Proposal: Global Index for PostgreSQL |