Re: Using Expanded Objects other than Arrays from plpgsql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, Michel Pelletier <pelletier(dot)michel(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Using Expanded Objects other than Arrays from plpgsql
Date: 2025-02-06 21:05:02
Message-ID: 1199223.1738875902@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Andrey Borodin <x4mmm(at)yandex-team(dot)ru> writes:
> 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.

Yeah, sounds like the best path if there are already outside users
of paramarg.

Do you have any further comments on this patch?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2025-02-06 22:23:57 Re: How to perform a long running dry run transaction without blocking
Previous Message Peter J. Holzer 2025-02-06 21:03:18 Re: Lookup tables

Browse pgsql-hackers by date

  From Date Subject
Next Message Chris Cleveland 2025-02-06 21:06:03 Re: "Type does not exist" error when returning array of type in non-public schema
Previous Message Alexander Lakhin 2025-02-06 21:00:30 Re: Improving tracking/processing of buildfarm test failures