Re: Bytea PL/Perl transform

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Иван Панченко <wao(at)mail(dot)ru>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Bytea PL/Perl transform
Date: 2023-07-06 11:47:51
Message-ID: dcaf22a8-f9fb-833b-0a84-1864f581f1a2@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22.06.23 22: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) ...

The reason the first transform modules were separate extensions is that
they interfaced between one extension (plpython, plperl) and another
extension (ltree, hstore), so it wasn't clear where to put them without
creating an additional dependency for one of them.

If the transform deals with a built-in type, then they should just be
added to the respective pl extension directly.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mikhail Gribkov 2023-07-06 11:52:41 Re: Permute underscore separated components of columns before fuzzy matching
Previous Message Matthias van de Meent 2023-07-06 11:40:31 HOT readme missing documentation on summarizing index handling