On Thu, Jul 31, 2025 at 2:24 AM Corey Huinker <corey.huinker@gmail.com> wrote:
>
>>
>> Besides, this does nothing you haven't been able to do for
>> decades with expression indexes.
>
>
> What I'm hoping for with this feature is a smoother transition when people start introducing virtual columns. If
therewas already an index on that expression, and some queries start using the new virtual column (with the same
expression),will that cause those queries to miss the index we already have? If it doesn't, then a customer can roll
outthe query changes at will and not need to do some cut-over from using the expression to using the virtual column.
>
hi.
I am not sure whether this concern has been addressed, as I am still somewhat
confused by the above paragraph.
As noted earlier, creating an index on a virtual generated column results in a
new index, and that index behaves the same as a regular expression index.
An updated and polished patch is attached. The regress tests are quite verbose
at the moment, since I make it covered all index types (btree, gist, spgist,
hash, gin, and brin).
--
jian
https://www.enterprisedb.com/
