Re: pg can create duplicated index without any errors even warnning

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Alex <zhihui(dot)fan1213(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg can create duplicated index without any errors even warnning
Date: 2019-08-06 03:16:11
Message-ID: CAH2-WzmQz3n1s7jyqwnWeEE0Ktm7G7juxx3QcrFg-i3xKxYAqw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 5, 2019 at 7:34 PM Alex <zhihui(dot)fan1213(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-08-06 03:36:54 Re: Assertion for logically decoding multi inserts into the catalog
Previous Message Masahiko Sawada 2019-08-06 03:00:27 Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)