Re: postgres_fdw could deparse ArrayCoerceExpr

From: Maxim Orlov <orlovmg(at)gmail(dot)com>
To: Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: postgres_fdw could deparse ArrayCoerceExpr
Date: 2025-01-24 15:09:14
Message-ID: CACG=ezYRyy0quCUPAOze+zRA6qdndFbJ_pKDGVVHa+rZVv390w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Look like an overlook for me. Apparently no one has encountered this use
case before.

Patch seems good to me with no visible defects. Deparse support was also
added. As well as a
test case. But do we really need copy/paste code for a T_ArrayCoerceExpr
case? To be more specific,
can we "reuse" T_RelabelType case, as it made for T_OpExpr and
T_DistinctExpr?

--
Best regards,
Maxim Orlov.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2025-01-24 15:20:03 Re: Non-text mode for pg_dumpall
Previous Message Andrew Dunstan 2025-01-24 14:53:09 Re: Orphaned users in PG16 and above can only be managed by Superusers