Re: Using Expanded Objects other than Arrays from plpgsql

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-03 17:57:27
Message-ID: 5AAA4DBE-4CC2-4D22-B138-BF2D48AE096F@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

> On 3 Feb 2025, at 22:36, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> I'm not wedded to that name; do you have a better idea?

I'd propose something like attached. But feel free to ignore my suggestion: I do not understand context of these structure members.

Best regards, Andrey Borodin.

Attachment Content-Type Size
rename.diff application/octet-stream 1.8 KB

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2025-02-03 18:18:10 Re: Using Expanded Objects other than Arrays from plpgsql
Previous Message Tom Lane 2025-02-03 17:53:06 Re: Using Expanded Objects other than Arrays from plpgsql

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2025-02-03 17:59:05 Re: SIGSEGV, FPE fix in pg_controldata
Previous Message Pavel Stehule 2025-02-03 17:55:48 Re: SQLFunctionCache and generic plans