From: | Tiffany Thang <tiffanythang(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: multiple indexes on the same column |
Date: | 2019-04-12 20:42:12 |
Message-ID: | CAB_W-NNvk-4MbPX4+2v43S9TwwLyxrSDpiwY7g9RKw0Cduy=0g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Got it! Thanks Andres and Tom!
Tiff
On Fri, Apr 12, 2019 at 1:07 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On 2019-04-12 09:51:51 -0400, Tom Lane wrote:
> >> Tiffany Thang <tiffanythang(at)gmail(dot)com> writes:
> >>> Can someone explain the use of creating multiple indexes on the same
> >>> column?
>
> >> There is none, unless the indexes have different properties (e.g.
> >> different opclasses and/or index AMs).
>
> > Well, it can be beneficial to create a new index concurrently, and then
> > drop the old one concurrently.
>
> Right, but in that situation there's no intent to keep both indexes
> in place. You're just putting up with extra overhead temporarily
> as a means to avoid taking an exclusive lock.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-04-13 00:06:02 | Re: Safe to delete files? |
Previous Message | Paul van der Linden | 2019-04-12 20:11:11 | Safe to delete files? |