On 2020-09-26 17:54:31 +0200, Paul Förster wrote:
> Hi Adrian,
> > On 26. Sep, 2020, at 17:43, Adrian Klaver
> > wrote:
> >
> > I suppose getting them to install Python 2 is out of the question?
> > It is an official package.
>
> I can try, but chances are at 99% that they refuse.
>
> > Well th
Hi Adrian,
> On 28. Sep, 2020, at 16:30, Adrian Klaver wrote:
> Not necessarily, if it is installing plpythonu functions.
I'll have to check that anyway. I'm already logged out of work, so I won't do
that now. 😇
Cheers,
Paul
On 9/28/20 7:22 AM, Paul Förster wrote:
Hi Adrian,
On 28. Sep, 2020, at 16:03, Adrian Klaver wrote:
So pgwatch2 installs functions that use plpythonu?
How does that work if there is no plpython language installed?
at work, the extension is installed everywhere. But it seems we have an old
Hi Adrian,
> On 28. Sep, 2020, at 16:03, Adrian Klaver wrote:
>
> So pgwatch2 installs functions that use plpythonu?
> How does that work if there is no plpython language installed?
at work, the extension is installed everywhere. But it seems we have an old
version. The current version seems t
On 9/28/20 6:37 AM, Paul Förster wrote:
Hi Adrian,
On 28. Sep, 2020, at 15:34, Adrian Klaver wrote:
Well I'm out of ideas. That means circling back to having Python 2 installed,
should the powers that be agree.
they don't. But fortunately, it seems that the number of applications which use
Hi Adrian,
> On 28. Sep, 2020, at 15:34, Adrian Klaver wrote:
>
> Well I'm out of ideas. That means circling back to having Python 2 installed,
> should the powers that be agree.
they don't. But fortunately, it seems that the number of applications which use
Python code inside a database, see
On 9/28/20 12:46 AM, Paul Förster wrote:
Hi Adrian,
On 27. Sep, 2020, at 19:30, Adrian Klaver wrote:
Does:
SELECT
lanname, proname, probin
FROM
pg_proc
JOIN
pg_language
ON
pg_language.oid = pg_proc.prolang
WHERE
pg_language.lanname='plpythonu'
AND
probin IS NOT NULL;
Hi Adrian,
> On 27. Sep, 2020, at 19:30, Adrian Klaver wrote:
>
> Does:
>
> SELECT
>lanname, proname, probin
> FROM
>pg_proc
> JOIN
>pg_language
> ON
>pg_language.oid = pg_proc.prolang
> WHERE
>pg_language.lanname='plpythonu'
> AND
> probin IS NOT NULL;
>
> show anything?
On 9/27/20 10:30 AM, Adrian Klaver wrote:
On 9/27/20 2:00 AM, Paul Förster wrote:
Hi Adrian,
On 27. Sep, 2020, at 00:09, Adrian Klaver
wrote:
Could it be that at some point in these instances history plpython*
where installed as CREATE LANGUAGE and you are dealing with the
vestiges of that?
On 9/27/20 2:00 AM, Paul Förster wrote:
Hi Adrian,
On 27. Sep, 2020, at 00:09, Adrian Klaver wrote:
Could it be that at some point in these instances history plpython* where
installed as CREATE LANGUAGE and you are dealing with the vestiges of that?
I do know for sure that that never happen
On 9/26/20 8:07 AM, Adrian Klaver wrote:
On 9/26/20 7:49 AM, Tom Lane wrote:
=?utf-8?Q?Paul_F=C3=B6rster?= writes:
On 26. Sep, 2020, at 16:07, Tom Lane wrote:
However, I don't understand how "drop extension plpythonu"
worked for you, given your previous query showing that
that extension wasn
Hi Adrian,
> On 27. Sep, 2020, at 00:09, Adrian Klaver wrote:
> Could it be that at some point in these instances history plpython* where
> installed as CREATE LANGUAGE and you are dealing with the vestiges of that?
I do know for sure that that never happened because the database clusters with
On 9/26/20 7:35 AM, Paul Förster wrote:
Hi Tom,
just checked with another 12.4. It's the same:
postgres=# select * from pg_available_extension_versions where installed;
name | version | installed | superuser | relocatable | schema |
requires | comment
On 9/26/20 8:54 AM, Paul Förster wrote:
Hi Adrian,
On 26. Sep, 2020, at 17:43, Adrian Klaver wrote:
I suppose getting them to install Python 2 is out of the question? It is an
official package.
I can try, but chances are at 99% that they refuse.
Well there is always going to be versionin
Hi Adrian,
> On 26. Sep, 2020, at 17:43, Adrian Klaver wrote:
>
> I suppose getting them to install Python 2 is out of the question? It is an
> official package.
I can try, but chances are at 99% that they refuse.
> Well there is always going to be versioning. If you mean the incompatibility
On 9/26/20 8:26 AM, Paul Förster wrote:
Hi Adrian,
On 26. Sep, 2020, at 17:17, Adrian Klaver wrote:
On 9/26/20 2:33 AM, Paul Förster wrote:
Hi,
the OS here is openSUSE Leap 15.2. I downloaded the PostgreSQL 13.0 source and
built it without issues like so:
openSUSE has no python2 anymore,
Hi Adrian,
> On 26. Sep, 2020, at 17:17, Adrian Klaver wrote:
>
> On 9/26/20 2:33 AM, Paul Förster wrote:
>> Hi,
>> the OS here is openSUSE Leap 15.2. I downloaded the PostgreSQL 13.0 source
>> and built it without issues like so:
>
>> openSUSE has no python2 anymore, only python3. The source
Hi Adrian,
> On 26. Sep, 2020, at 17:07, Adrian Klaver wrote:
>
> I believe the issue is here:
>
> select * from pg_pltemplate ;
>
>
> plpythonu | f | f | plpython_call_handler |
> plpython_inline_handler | plpython_validator | $libdir/plpython2 | NULL
> plpython2u
On 9/26/20 2:33 AM, Paul Förster wrote:
Hi,
the OS here is openSUSE Leap 15.2. I downloaded the PostgreSQL 13.0 source and
built it without issues like so:
openSUSE has no python2 anymore, only python3. The source database does not
even have plpython installed:
Actually it does:
https
Hi Tom,
> On 26. Sep, 2020, at 16:49, Tom Lane wrote:
>
> Actually, now that I think about it, you're querying the wrong view.
> I'm too lazy to check the source code right now, but I'm pretty sure
> that pg_available_extension_versions is mostly driven off what control
> files exist in the on-d
On 9/26/20 7:49 AM, Tom Lane wrote:
=?utf-8?Q?Paul_F=C3=B6rster?= writes:
On 26. Sep, 2020, at 16:07, Tom Lane wrote:
However, I don't understand how "drop extension plpythonu"
worked for you, given your previous query showing that
that extension wasn't installed.
just checked with another
=?utf-8?Q?Paul_F=C3=B6rster?= writes:
> On 26. Sep, 2020, at 16:07, Tom Lane wrote:
>> However, I don't understand how "drop extension plpythonu"
>> worked for you, given your previous query showing that
>> that extension wasn't installed.
> just checked with another 12.4. It's the same:
> post
Hi Tom,
> On 26. Sep, 2020, at 16:07, Tom Lane wrote:
>
> =?utf-8?Q?Paul_F=C3=B6rster?= writes:
>> seems, I found some kind of solution:
>
>> - before running "pg_upgrade --check -k":
>> drop extension plpythonu;
>> - run pg_upgrade
>> - after the upgrade:
>> create extension plpython3u;
>
Hi Tom,
> On 26. Sep, 2020, at 16:07, Tom Lane wrote:
>
> If you had plpythonu installed before, that's a plausible thing
> to do. (There was discussion some time ago about making the
> python-2-to-3 transition less painful for users, but we failed
> to come to any consensus about how; so manua
=?utf-8?Q?Paul_F=C3=B6rster?= writes:
> seems, I found some kind of solution:
> - before running "pg_upgrade --check -k":
> drop extension plpythonu;
> - run pg_upgrade
> - after the upgrade:
> create extension plpython3u;
> Is this the correct way?
If you had plpythonu installed before, th
Hi,
> On 26. Sep, 2020, at 11:42, Paul Förster wrote:
>
> the two things I forgot to mention are:
>
> a) the versions I will be upgrading from are 11.9 and 12.4. The above thing
> happens with 12.4. Since I didn't check 11.9 yet, I cannot say if it appears
> there too.
>
> b) the 12.4 softwa
Hi,
sorry, forgot to mention two things (see below)
> On 26. Sep, 2020, at 11:33, Paul Förster wrote:
>
> Hi,
>
> the OS here is openSUSE Leap 15.2. I downloaded the PostgreSQL 13.0 source
> and built it without issues like so:
>
> (pgTargetDir is /data/postgres/13.0)
>
> $ ./configure \
>
Hi,
the OS here is openSUSE Leap 15.2. I downloaded the PostgreSQL 13.0 source and
built it without issues like so:
(pgTargetDir is /data/postgres/13.0)
$ ./configure \
--prefix=${pgTargetDir} \
--enable-nls \
--with-icu \
--with-perl \
--with-python \
--with-openssl \
28 matches
Mail list logo
