| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Time to drop plpython2? |
| Date: | 2022-03-09 09:29:17 |
| Message-ID: | f8fbf940-73ef-6b55-15c3-917203d845bf@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08.03.22 20:03, Andres Freund wrote:
> Hi,
>
> On 2022-03-08 13:49:15 -0500, Tom Lane wrote:
>> Andres Freund <andres(at)anarazel(dot)de> writes:
>>> A bit depressing to have a 500 line alternative output file for a one line
>>> diff :(.
>>
>> Yeah. How badly do we need that particular test case?
>
> A bit hard to tell. The test was introduced in
>
> commit 2bd78eb8d51cc9ee03ba0287b23ff4c266dcd9b9
> Author: Peter Eisentraut <peter_e(at)gmx(dot)net>
> Date: 2011-04-06 22:36:06 +0300
>
> Add traceback information to PL/Python errors
We would probably try to write this test differently today, but at this
point I wouldn't bother and just wait for Python 3.5 to fall off the end
of the conveyor belt.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2022-03-09 10:03:40 | Re: Column Filtering in Logical Replication |
| Previous Message | Peter Eisentraut | 2022-03-09 09:20:57 | Re: Column Filtering in Logical Replication |