I wrote:
> But I could support having a way for individual installations to change
> what the synonym means locally. Perhaps we could think about how to do
> that in conjunction with the project of getting rid of pg_pltemplate
> that's been kicked around before [1][2][3].
... actually, if we had
Peter Eisentraut writes:
> I'm not trying to dismiss the importance of managing the Python
> transition. But this issue has been known for many years, and the
> current setup is more or less in line with the wider world. For
> example, the Debian release that came out over the weekend still
On 2019-07-07 21:26, Steven Pousty wrote:
> The point of the links I sent from the Python community is that they
> wanted Python extinct in the wild as of Jan 1 next year. They are never
> fixing it, even for a security vulnerability.
The operating systems that most of our users are going to run
The point of the links I sent from the Python community is that they wanted
Python extinct in the wild as of Jan 1 next year. They are never fixing it,
even for a security vulnerability.
It seems to me we roll out breaking changes with major versions. So yes, if
the user chooses to upgrade to 12
Peter Eisentraut writes:
> On 2019-07-07 00:34, Steven Pousty wrote:
>> Why would it be a 13 or later issue?
> Because PostgreSQL 12 is feature frozen and in beta, and this issue is
> not a regression.
More to the point: it does not seem to me that we should change what
"plpythonu" means until
On 2019-07-07 00:34, Steven Pousty wrote:
> Why would it be a 13 or later issue?
Because PostgreSQL 12 is feature frozen and in beta, and this issue is
not a regression.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training &
Why would it be a 13 or later issue?
I am specifically talking about changing the default.
On Sat, Jul 6, 2019, 6:28 PM Peter Eisentraut <
peter.eisentr...@2ndquadrant.com> wrote:
> On 2019-07-06 21:02, Steven Pousty wrote:
> > /" The default will probably be changed to Python 3 in a distant
On 2019-07-06 21:02, Steven Pousty wrote:
> /" The default will probably be changed to Python 3 in a distant future
> release of PostgreSQL, depending on the progress of the migration to
> Python 3 in the Python community."/
>
> I know we are late in the Postgresql 12 cycle but I think switching
