Re: pg can create duplicated index without any errors even warnning - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: pg can create duplicated index without any errors even warnning
Date
Msg-id CAH2-WzmQz3n1s7jyqwnWeEE0Ktm7G7juxx3QcrFg-i3xKxYAqw@mail.gmail.com
Whole thread Raw
In response to pg can create duplicated index without any errors even warnning  (Alex <zhihui.fan1213@gmail.com>)
Responses Re: pg can create duplicated index without any errors even warnning  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Mon, Aug 5, 2019 at 7:34 PM Alex <zhihui.fan1213@gmail.com> wrote:
> is this by design?

Yes. Being able to do this is useful for several reasons. For example,
it's useful to be able to create a new, equivalent index before
dropping the original when the original is bloated. (You could use
REINDEX instead, but that has some disadvantages that you might want
to avoid.)

Questions like this are better suited to the pgsql-general list.

--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and KeyManagement Service (KMS)
Next
From: Michael Paquier
Date:
Subject: Re: Assertion for logically decoding multi inserts into the catalog