| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Making plpython 2 and 3 coexist a bit better |
| Date: | 2016-01-11 23:33:19 |
| Message-ID: | 9717.1452555199@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> In further experimentation, I found out that even with this patch in
> place, the plpython transform extensions still present a dump/reload
> hazard:
> ...
> But I wonder why we couldn't make it do
> LOAD 'plpython3';
I've verified that the attached additional patch makes everything behave
nicely in this corner of the world. AFAICS this adds no assumptions
that aren't already built into pg_pltemplate.
Last call for objections ...
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| transform-load-fix.patch | text/x-diff | 4.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-01-11 23:50:46 | Re: [PROPOSAL] Client Log Output Filtering |
| Previous Message | Alvaro Herrera | 2016-01-11 23:31:30 | Re: Fuzzy substring searching with the pg_trgm extension |