Re: [PATCH] Resolve iso-8859-1-type literals in GRAPH_TABLE COLUMNS - Mailing list pgsql-hackers

From Junwang Zhao
Subject Re: [PATCH] Resolve iso-8859-1-type literals in GRAPH_TABLE COLUMNS
Date
Msg-id CAEG8a3KTP1sX+RbPFNST4kHdeRZQR5-dd6kEihV56=K5irrhyQ@mail.gmail.com
Whole thread
Responses Re: [PATCH] Resolve iso-8859-1-type literals in GRAPH_TABLE COLUMNS
List pgsql-hackers
Hi SATYANARAYANA,

On Sun, Apr 26, 2026 at 3:53 AM SATYANARAYANA NARLAPURAM
<satyanarlapuram@gmail.com> wrote:
>
> Hi hackers,
>
> transformRangeGraphTable() calls transformExpr() and
> assign_list_collations() for COLUMNS expressions but missed calling
> resolveTargetListUnknowns(). As a result, literals such as 'val1'
> in a COLUMNS clause retained type "unknown", causing failures with
> ORDER BY, UNION, and output conversions.
>
> Fix by calling resolveTargetListUnknowns() on the columns target
> list right after assign_list_collations(), similar to SELECT target lists in
> transformSelectStmt().
>
> Attached a patch to fix this, which also includes test cases to reproduce.

I can reproduce this and the patch fixes it.

One question: why is resolveTargetListUnknowns called after
assign_list_collations?

I'm asking because in transformSelectStmt, resolveTargetListUnknowns
is invoked before assign_query_collations. It might not matter, but keeping
the order consistent would be good for readers.

>
>
> Thanks,
> Satya
>
>


--
Regards
Junwang Zhao



pgsql-hackers by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: Yet another way for pg_ctl stop to fail on Windows
Next
From: DaeMyung Kang
Date:
Subject: [PATCH] Fix memory leak of reply_message in walreceiver