Re: Improving the names generated for indexes on expressions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Improving the names generated for indexes on expressions
Date: 2025-11-01 22:28:26
Message-ID: 238409.1762036106@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

[ Nobody has had any better ideas in 2 months, so back to this ... ]

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Do you think there's any way of doing this usefully while not
> autogenerating names that require quoting, or is that a hopeless
> endeavor? If it's hopeless, is it better to accept autogenerated names
> that require quoting, or is it better to solve the problem on the
> other thread with something more like what you proposed there?

If people are dead set against double-quoting, I think the only way
forward is to not include operator names in the generated index names.
I do not think that's a better way personally, but I seem to be
outvoted. Here's a v2 that does it like that.

regards, tom lane

Attachment Content-Type Size
v2-0001-Improve-the-names-generated-for-indexes-on-expres.patch text/x-diff 41.9 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua Shanks 2025-11-01 23:49:02 [PATCH] Add error message for out-of-memory in passwordFromFile()
Previous Message Arseniy Mukhin 2025-11-01 20:41:51 Re: Optimize LISTEN/NOTIFY