Re: pg_upgrade from 12 to 13 failes with plpython2

From: Devrim Gündüz <devrim(at)gunduz(dot)org>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Marcin Giedz <marcin(dot)giedz(at)arise(dot)pl>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_upgrade from 12 to 13 failes with plpython2
Date: 2020-12-24 20:14:31
Message-ID: ee9b7b274a50a407d475b47dfdc59ada0215d796.camel@gunduz.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Hi,

On Tue, 2020-11-17 at 14:30 -0800, Adrian Klaver wrote:
> As a packager you are in charge of how the packaging is done. Still
> announcing a change that effectively nullifies the documentation
> would to me be something that should be announced somewhere else
> than a list that I'm guessing 99% of the users don't read.

Published a blog post today:

https://people.planetpostgresql.org/devrim/index.php?/archives/106-What-is-new-in-PostgreSQL-13-RPMs.html

Same text will go to yum.postgresql.org tomorrow.

(Sorry for the delay)

Regards,
--
Devrim Gündüz
Open Source Solution Architect, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Lars Vonk 2020-12-24 20:24:39 Re: Missing rows after migrating from postgres 11 to 12 with logical replication
Previous Message Open _ 2020-12-24 17:44:32 Re: created type not found in create table