| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tristan Partin <tristan(at)neon(dot)tech>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | gdo(at)leader(dot)it, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: BUG #17946: LC_MONETARY & DO LANGUAGE plperl - BUG |
| Date: | 2023-07-03 16:31:09 |
| Message-ID: | 65667857-d2a8-e357-6ba6-45d98a363f61@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-07-03 22:02:03 | Re: BUG #17949: Adding an index introduces serialisation anomalies. |
| Previous Message | Joe Conway | 2023-07-03 16:28:01 | Re: BUG #17946: LC_MONETARY & DO LANGUAGE plperl - BUG |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2023-07-03 16:34:47 | Re: explain analyze rows=%.0f |
| Previous Message | Joe Conway | 2023-07-03 16:28:01 | Re: BUG #17946: LC_MONETARY & DO LANGUAGE plperl - BUG |