pg.ddx.io pgsql-bugs@postgresql.org mailing list archive help / color / mirror / Atom feed From: Joe Conway <mail@joeconway.com>
To: Tristan Partin <tristan@neon.tech>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: gdo@leader.it, Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: BUG #17946: LC_MONETARY & DO LANGUAGE plperl - BUG
Date: Mon, 3 Jul 2023 12:31:09 -0400
Message-ID: <65667857-d2a8-e357-6ba6-45d98a363f61@joeconway.com> (raw )
In-Reply-To: <CTSOE3SS70RW.YE7NMLMQSQSO@gonk >
References: <17946-3e84cb577e9551c3@postgresql.org >
<1564676.1685043220@sss.pgh.pa.us >
<555bb26e-c27c-ab65-028f-3fd5b82df9de@iki.fi >
<CT887GSPI31W.BQCSW35JL67L@gonk >
<ca35e375-be82-322d-8c81-78127d8fb33f@joeconway.com >
<5676b739-0854-f924-4b97-466e3504c692@joeconway.com >
<f1856a5d-3703-66ff-e7c7-01d2489315c1@joeconway.com >
<665279.1686422574@sss.pgh.pa.us >
<c23d6ec1-f882-af48-82d9-54e9f3e15809@joeconway.com >
<574a1afa-5c6e-829c-0fed-a9ff44719f9f@joeconway.com >
<49dfcad8-90fa-8577-008f-d142e61af46b@iki.fi >
<41a4898e-1cdb-960d-f17e-d71886407e04@joeconway.com >
<18c6979a-126a-e530-7cc4-3b6984b1997b@joeconway.com >
<ac52326b-874b-372f-220c-60b424a9a833@joeconway.com >
<fb4f7abd-6c66-1a35-feea-115d44e6c02a@iki.fi >
<839d893b-1681-f6b6-e1ba-685c34c582ca@joeconway.com >
<933780cc-2265-a47a-9f39-dd9208bd2c64@iki.fi >
<ec6fa20d-e691-198a-4a13-e761771b9dec@joeconway.com >
<CTSOE3SS70RW.YE7NMLMQSQSO@gonk >
On 7/3/23 12:25, Tristan Partin wrote:
> On Sat Jun 24, 2023 at 8:09 AM CDT, Joe Conway wrote:
>> Although I have not looked yet, presumably we could have similar
>> problems with plpython. I would like to get agreement on this approach
>> against plperl before diving into that though.
>>
>> Thoughts?
>
> I don't see anything immediately wrong with this. I think doing a
> similar thing for plpython would make sense. Might make sense to CC any
> other pl* maintainers too.
In our tree there are only plperl and plpython to worry about.
"other pl* maintainers" is a fuzzy concept since other pl's are
scattered far and wide.
I think it is reasonable to expect such maintainers to be paying
attention to hackers and pick up on it themselves (I say that as a pl
maintainer myself -- plr)
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
view thread (38+ messages) latest in thread
Message-ID: <65667857-d2a8-e357-6ba6-45d98a363f61@joeconway.com>
Permalink: ../65667857-d2a8-e357-6ba6-45d98a363f61@joeconway.com/
Also on: postgresql.org/message-id/65667857-d2a8-e357-6ba6-45d98a363f61@joeconway.com
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: mail@joeconway.com, tristan@neon.tech, hlinnaka@iki.fi, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: Re: BUG #17946: LC_MONETARY & DO LANGUAGE plperl - BUG
In-Reply-To: <65667857-d2a8-e357-6ba6-45d98a363f61@joeconway.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox