| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Maaz Syed Adeeb <maaz(dot)adeeb(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, matthew(dot)ripley28(at)gmail(dot)com |
| Subject: | Re: CREATE INDEX with an expression in an INCLUDE column fails with XX000 "unrecognized node type" instead of 0A000 on master |
| Date: | 2026-07-15 18:29:04 |
| Message-ID: | 3574719.1784140144@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Maaz Syed Adeeb <maaz(dot)adeeb(at)gmail(dot)com> writes:
> On current master, creating an index with an expression in an INCLUDE
> (non-key) column fails with an internal error ("unrecognized node
> type", SQLSTATE XX000) instead of the user-facing
> FEATURE_NOT_SUPPORTED (0A000) "expressions are not supported in
> included columns". The statement is still correctly rejected, but with
> the wrong error class and a message.
Thanks for the report! This is evidently happening because we have
not applied parse transformation to the included columns. I think
that the most appropriate way to fix it is to start doing so, even
though the feature will be rejected later. More or less as attached
(but we ought to add a test case too).
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| wip-fix-index-included-expressions.patch | text/x-diff | 986 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maaz Syed Adeeb | 2026-07-15 18:57:27 | Re: CREATE INDEX with an expression in an INCLUDE column fails with XX000 "unrecognized node type" instead of 0A000 on master |
| Previous Message | Kenny Chen | 2026-07-15 14:24:20 | Re: BUG #19547: libpqrcv_create_slot dereferences NULL on a malformed CREATE_REPLICATION_SLOT reply |