From: | Dippu Kumar <dippu(dot)k(at)deeplynx(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Need Support to Upgrade from 13.6 to 15.3 |
Date: | 2023-05-23 11:20:39 |
Message-ID: | CAF6fgVW4sEEONUWXeAEfzviVAGDFF=7sNE=+PFOhw0AFx1HGVw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
I really appreciate your help!
Please provide me with steps to do this.
Will it impact my existing data (+ 650 GB) and compatibility?
On Tue, May 23, 2023 at 3:15 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
wrote:
> On 2023-May-23, Dippu Kumar wrote:
>
> > apt policy libpq5
> > libpq5:
> > Installed: 2:13.10-1.bionic
> > Candidate: 2:13.10-1.bionic
> > Version table:
> > *** 2:13.10-1.bionic 500
> > 500 http://repo.percona.com/ppg-13/apt bionic/main amd64
> Packages
> > 100 /var/lib/dpkg/status
>
> So you seem to have a Percona repository enabled, and the libpq5 package
> comes from there. You need to ask Percona about this, not the Postgres
> community -- or maybe get rid of the Percona repo completely, as it is
> clearly breaking your system.
>
> Also, maybe upgrade from Bionic.
>
> --
> Álvaro Herrera 48°01'N 7°57'E —
> https://www.EnterpriseDB.com/
> "The important things in the world are problems with society that we don't
> understand at all. The machines will become more complicated but they won't
> be more complicated than the societies that run them." (Freeman Dyson)
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-05-23 14:07:12 | Re: Prepared SQL name collision. The name implicitly is truncated by NAMEDATALEN |
Previous Message | Alexander Lakhin | 2023-05-23 11:00:00 | Re: BUG #17695: Failed Assert in logical replication snapbuild. |