Re: Using Expanded Objects other than Arrays from plpgsql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Michel Pelletier <pelletier(dot)michel(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Using Expanded Objects other than Arrays from plpgsql
Date: 2024-11-19 19:45:16
Message-ID: 3797606.1732045516@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> út 19. 11. 2024 v 18:51 odesílatel Michel Pelletier <
> pelletier(dot)michel(at)gmail(dot)com> napsal:
>> A couple years ago I tried to compress what I learned about expanded
>> objects into a dummy extension that just provides the necessary
>> boilerplate. It wasn't great but a start:
>> https://github.com/michelp/pgexpanded
>> Pavel Stehule indicated this might be a good example to put into contrib:

> another position can be src/test/modules - I think so your example is
> "similar" to plsample

Yeah. I think we've largely adopted the position that contrib should
contain installable modules that do something potentially useful to
end-users. A pure skeleton wouldn't be that, but if it's fleshed out
enough to be test code for some core features then src/test/modules
could be a reasonable home.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michel Pelletier 2024-11-19 20:52:46 Re: Using Expanded Objects other than Arrays from plpgsql
Previous Message Paul Foerster 2024-11-19 19:16:28 Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints

Browse pgsql-hackers by date

  From Date Subject
Next Message Kirill Reshke 2024-11-19 20:02:49 Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row
Previous Message Bertrand Drouvot 2024-11-19 19:28:03 Re: Parametrization minimum password lenght