Re: Can I get some PostgreSQL developer feedback on these five general issues I have with PostgreSQL and its ecosystem?

> On Sep 22, 2020, at 5:28 PM, tutilu...@tutanota.com wrote: > > I hate the "wrong tool for the job" argument. It assumes that everyone has > infinite time, energy and brain capacity to learn endless redundant tools > just to "use the right tool for the job" rather than "use what you actually

Re: pg_upgrade Python version issue on openSUSE

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

Re: pg_upgrade Python version issue on openSUSE

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

Re: pg_upgrade Python version issue on openSUSE

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

Re: pg_upgrade Python version issue on openSUSE

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,

Re: pg_upgrade Python version issue on openSUSE

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

Re: pg_upgrade Python version issue on openSUSE

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

Re: pg_upgrade Python version issue on openSUSE

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

Re: pg_upgrade Python version issue on openSUSE

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

Re: pg_upgrade Python version issue on openSUSE

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

Re: pg_upgrade Python version issue on openSUSE

=?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

Re: pg_upgrade Python version issue on openSUSE

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; >

Re: PG 13 trusted extensions and pg_available_extensions

On Sat, Sep 26, 2020 at 10:11 PM Tom Lane wrote: > > Julien Rouhaud writes: > > So, apparently pg_available_extension_versions already had those > > fields so all the required infrastructure was already there. I just > > added the exact same fields to pg_available_extensions, see attached > > pa

Re: pg_upgrade Python version issue on openSUSE

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

Re: PG 13 trusted extensions and pg_available_extensions

Julien Rouhaud writes: > So, apparently pg_available_extension_versions already had those > fields so all the required infrastructure was already there. I just > added the exact same fields to pg_available_extensions, see attached > patch. The reason that pg_available_extensions has only the fie

Re: pg_upgrade Python version issue on openSUSE

=?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

Re: pg_upgrade Python version issue on openSUSE

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

Re: PG 13 trusted extensions and pg_available_extensions

On Fri, Sep 25, 2020 at 2:51 PM Daniel Westermann (DWE) wrote: > > On Thu, Sep 24, 2020 at 10:58 AM Michael Paquier wrote: > >> > >> On Wed, Sep 23, 2020 at 03:28:45PM +, Daniel Westermann (DWE) wrote: > >> > I was playing a bit with trusted extensions and wondered if there is > >> > a reason

Re: pg_upgrade Python version issue on openSUSE

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 \ >

pg_upgrade Python version issue on openSUSE

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 \

Yum repository RPM behind release

Hi Postgres 13 is out and the yum repos for the release exist, eg: https://yum.postgresql.org/13/redhat/rhel-8-x86_64/ . However the repository RPM suggested at https://www.postgresql.org/download/linux/redhat/