| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, 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-28 16:34:41 |
| Message-ID: | 1236158.1687970081@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?utf-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= <ilmari(at)ilmari(dot)org> writes:
> 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?
Perhaps another way could be to accept that the packaging is what it
is, but look for ways to share the repetitive source code. The .so's
wouldn't get any smaller, but they're not that big anyway.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2023-06-28 16:40:45 | Re: Incremental View Maintenance, take 2 |
| Previous Message | Peter Eisentraut | 2023-06-28 16:31:01 | Re: Assistance Needed: Issue with pg_upgrade and --link option |