Re: Error; pg_upgrade 10 to 15

From: Imran Khan <imran(dot)k(dot)23(at)gmail(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Error; pg_upgrade 10 to 15
Date: 2024-07-18 12:17:31
Message-ID: CAC4eXDgcxC0avU8pZCAG5+t2LX6Uxs0N7dz44eNSp75VJeUXRg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi Ron,
Why don't you go with logical backup and restore than pg_upgrade? How much
is the size ? Will you get downtime for performing the upgrade? Can you get
a parallel server with latest OS and PG15 or 16 installed ?

Thanks,
Imran

On Thu, Jul 18, 2024, 1:09 AM Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:

> On Wed, Jul 17, 2024 at 9:53 AM Holger Jakobs <holger(at)jakobs(dot)com> wrote:
>
>> Just general remarks:
>>
>> 1. There is no need to upgrade to intermediate major versions. Go from
>> 10.(lastest minor) directly to 16.3
>>
>
> Maybe the version of some extension (like PostGIS) installed on PG10 is
> incompatible with PG 15, so the upgrade must be done in stages (upgrading
> the extension at every step).
>
>
>> 2. Why would you want to upgrade to 15 when 16 is already out.
>>
>
> An application vendor might not have certified PG 16. Or maybe
> non-technical upper management is scared of the latest version.
>
>
>>
>> Regards,
>> Holger
>>
>>
>> Am 17. Juli 2024 15:24:04 MESZ schrieb SOzcn <selahattinozcnma(at)gmail(dot)com
>> >:
>>
>>> Hello Folks,
>>>
>>> We are upgrading from version 10 to 15. We encountered the following
>>> error for the first time. Can you give any ideas on how to solve this
>>> error? Since it is a system table, we cannot intervene on it.
>>>
>>>
>>>
>>>
>>> *pg_restore: from TOC entry 3312; 0 0 ACL TABLE "pg_pltemplate"
>>> postgrespg_restore: error: could not execute query: ERROR: relation
>>> "pg_catalog.pg_pltemplate" does not existCommand was: GRANT SELECT ON TABLE
>>> "pg_catalog"."pg_pltemplate" TO "username";*
>>> We upgraded many Postgresql in the same way. But this error just blew up
>>> somehow.
>>> For this cluster, we upgraded 10 to 11 and then 11 to 12 without a
>>> problem, but the same error comes after 12 to 13 and 12 to 15.
>>>
>>> The other issue is that the check is successful when we check the
>>> cluster for the upgrade.
>>>
>>> The Upgrade Command;
>>>
>>> /usr/lib/postgresql/15/bin/pg_upgrade
>>> --old-bindir /usr/lib/postgresql/12/bin/
>>> --new-bindir /usr/lib/postgresql/15/bin/
>>> --old-datadir /data/rac/12/main/
>>> --new-datadir /data/rac/15/main2
>>> --old-options '-c config_file=/etc/postgresql/12/main/postgresql.conf'
>>> --new-options '-c
>>> config_file=/etc/postgresql/15/main2/postgresql.conf' --check
>>>
>>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Thomas Simpson 2024-07-18 13:54:07 Re: filesystem full during vacuum - space recovery issues
Previous Message Nikhil Shetty 2024-07-18 11:38:22 Re: Queries waiting on SyncRep even though synchronous_standby_names is absent