| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Sami Imseih <samimseih(at)gmail(dot)com> |
| Cc: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Japin Li <japinli(at)hotmail(dot)com>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Disallow redundant indexes |
| Date: | 2025-04-28 22:17:00 |
| Message-ID: | aA_-XAZCAAnu3rzn@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 28, 2025 at 01:12:18PM -0500, Sami Imseih wrote:
> If I had a dollar for every time I asked a user to check for duplicate
> indexes :) So
> I think it's a good idea to provide some way to detect these ( besides
> a query in the
> Wiki ), but I don't think we should prevent it.
>
> While a WARNING will be a good to have, it could easily go unnoticed,
> but it's still good to have.
I don't doubt that this is a problem in the field, but I'm not sure I'm
convinced it's worthwhile to emit a warning that only appears for exact
duplicates and is very easily missed, not to mention that the user could be
intentionally creating the index.
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-04-28 22:19:19 | Re: Large expressions in indexes can't be stored (non-TOASTable) |
| Previous Message | Nathan Bossart | 2025-04-28 22:01:36 | Re: teach pg_upgrade to handle in-place tablespaces |