Re: Improving the names generated for indexes on expressions
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>,
"pgsql-hackers@lists.postgresql.org"
<pgsql-hackers@lists.postgresql.org>
Date: 2025-09-16T12:55:12Z
Lists: pgsql-hackers
"David G. Johnston" <david.g.johnston@gmail.com> writes: > More generally, maybe map all the various common accessor operators to “.” > instead of using them directly and capture the constants when chained from > a column. That seems fairly useless. You still have a name that requires double quotes, and you can't tell one operator from another, and you haven't even saved much space because few operator names are longer than two or three characters. (I have thought a little about truncating the contents of Consts to maybe a dozen bytes for this purpose. Those seem much more likely to be long...) More generally, though, I absolutely object to giving the JSON operators some kind of special privilege in this context. That's totally not per Postgres style, and besides it's not solving the problem as a whole, but just this one example. regards, tom lane
Commits
-
Improve the names generated for indexes on expressions.
- 181b6185c79e master landed