Re: CREATE INDEX with an expression in an INCLUDE column fails with XX000 "unrecognized node type" instead of 0A000 on master - Mailing list pgsql-bugs

From Tom Lane
Subject Re: CREATE INDEX with an expression in an INCLUDE column fails with XX000 "unrecognized node type" instead of 0A000 on master
Date
Msg-id 3789751.1784217864@sss.pgh.pa.us
Whole thread
In response to Re: CREATE INDEX with an expression in an INCLUDE column fails with XX000 "unrecognized node type" instead of 0A000 on master  (Maaz Syed Adeeb <maaz.adeeb@gmail.com>)
List pgsql-bugs
Maaz Syed Adeeb <maaz.adeeb@gmail.com> writes:
> Attaching a patch with two regress tests. Let me know if I need to
> change anything.

Thanks.  index_including.sql embodies all sorts of anti-patterns
for testing: use of very generic object names that could conflict
with concurrent test scripts, constant dropping and re-creation
of objects ensuring that the overhead per useful test is as high
as possible, etc.  But it's not the job of this patch to improve
that, so I guess the fact that you faithfully copied the existing
style is fine.  I used your test as-is and pushed it.  Thanks
again for the report!

            regards, tom lane



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #19554: No match for argument: postgresql18-server Error: Unable to find a match: postgresql18-server
Next
From: "Matheus Alcantara"
Date:
Subject: Re: BUG #19553: Wrong results from nested LEFT JOINs over an empty subquery (regression since v16)