Re: Using Expanded Objects other than Arrays from plpgsql - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: Using Expanded Objects other than Arrays from plpgsql
Date
Msg-id 729D43DE-BCA0-495E-926E-8789A01DACC4@yandex-team.ru
Whole thread Raw
In response to Re: Using Expanded Objects other than Arrays from plpgsql  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Using Expanded Objects other than Arrays from plpgsql
List pgsql-hackers

> On 3 Feb 2025, at 23:18, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> But I don't want to think of
> EEOP_PARAM_CALLBACK as being specifically tied to PL/pgSQL.

I've found 1 users on Github [0]. And a lot of copied code like [1]. And there might be some unindexed cases.
Let's keep paramarg2.


Best regards, Andrey Borodin.
[0]
https://github.com/wanglinn/xadb/blob/7695b7edcb0a89f3173b648c0da5b953538f2aa9/src/backend/pgxc/pool/execRemote.c#L835
[1]
https://github.com/babelfish-for-postgresql/babelfish_extensions/blob/376cf488804fa02f9b1db5bbfbe74e98627fe96c/contrib/babelfishpg_tsql/src/pl_exec.c#L8030


pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: Doc fix of aggressive vacuum threshold for multixact members storage
Next
From: Masahiko Sawada
Date:
Subject: Re: pg_rewind with --write-recovery-conf option doesn't write dbname to primary_conninfo value.