Re: postgres_fdw could deparse ArrayCoerceExpr
Alexander Korotkov <aekorotkov@gmail.com>
From: Alexander Korotkov <aekorotkov@gmail.com>
To: Maxim Orlov <orlovmg@gmail.com>
Cc: Alexander Pyhalov <a.pyhalov@postgrespro.ru>,
pgsql-hackers@lists.postgresql.org
Date: 2025-06-04T11:29:04Z
Lists: pgsql-hackers
Hi Maxim, On Wed, Jan 29, 2025 at 11:59 AM Maxim Orlov <orlovmg@gmail.com> wrote: > > One important note here. This patch will change cast behaviour in case of local and foreign types are mismatched. > The problem is if we cannot convert types locally, this does not mean that it is also true for a foreign wrapped data. > In any case, it's up to the committer to decide whether this change is needed or not. I have two question regarding this aspect. 1) Is it the same with regular type conversion? 2) Can we fallback to remote type conversion in local type conversion fails? ------ Regards, Alexander Korotkov Supabase
Commits
-
Fix a typo in the deparseArrayCoerceExpr() header comment
- 4c5159a2d8c0 19 (unreleased) landed
-
Support for deparsing of ArrayCoerceExpr node in contrib/postgres_fdw
- 62c3b4cd9ddc 19 (unreleased) landed