Re: Proposal: Remove regress-python3-mangle.mk

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Yury Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>
Cc: Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: Remove regress-python3-mangle.mk
Date: 2016-04-20 21:16:43
Message-ID: 27600.1461187003@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Yury Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru> writes:
> Tom Lane wrote:
>> Also, I would bet that those tools would not know anything
>> about converting PL language names between 'plpythonu' and 'plpython2u'
>> and 'plpython3u'; so even if we used one of them, we would still need a
>> layer pretty similar to what we have.

> I do not see this as a problem because we can build Postgres only with one
> version of Python (2 or 3).

What's your point? The tests still have to load the correct version
of the PL language by name, and create functions that reference that
version by name. Moreover, "make installcheck" should work even
against an installation with both .so's installed.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-04-20 21:49:46 Re: Avoid parallel full and right join paths.
Previous Message Tom Lane 2016-04-20 20:44:58 Should XLogInsert() be done only inside a critical section?