| From: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Иван Панченко <wao(at)mail(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Bytea PL/Perl transform |
| Date: | 2023-06-23 15:14:34 |
| Message-ID: | 87o7l6qkh1.fsf@wibble.ilmari.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 2023-06-22 Th 16:56, Greg Sabino Mullane wrote:
>>
>> * Do all of these transforms need to be their own contrib modules? So
>> much duplicated code across contrib/*_plperl already (and *plpython
>> too for that matter) ...
>>
>>
>
> Yeah, that's a bit of a mess. Not sure what we can do about it now.
Would it be possible to move the functions and other objects to a new
combined extension, and make the existing ones depend on that?
I see ALTER EXTENSION has both ADD and DROP subcommands which don't
affect the object itself, only the extension membership. The challenge
would be getting the ordering right between the upgrade/install scripts
dropping the objects from the existing extension and adding them to the
new extension.
- ilmari
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2023-06-23 15:52:34 | Re: psql: Add role's membership options to the \du+ command |
| Previous Message | Matthias van de Meent | 2023-06-23 14:46:02 | Re: Improving btree performance through specializing by key shape, take 2 |