Re: Postgresql Upgrade

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgresql Upgrade
Date: 2024-08-27 14:08:09
Message-ID: CANzqJaB0aAs8oEpenvXk+b2QxscE8S5vZ-KvF9kBScHmz-sCng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Aug 27, 2024 at 6:31 AM SOzcn <selahattinozcnma(at)gmail(dot)com> wrote:

> Hello,
>
> There is few cluster which is using fk server and postgis.
>
> For the upgrade this servers, I need the drop extension and then re-create
> them.
> Just in case if I do that with pg_dump, am i still have to re-create
> postgis and fk servers?
>

Out of curiosity, what's "fk"? It can't be "FOREIGN KEY", can it?

> I didin't want waste time before the do that so I need your advice.
>

I doubt it, since pg_dump generates *all* of CREATE (and ALTER) statements
required for a database, and pg_restore then runs them.

Thus, if (new) postgis and fk packages are installed on the new server,
pg_restore will CREATE EXTENSION with the new version of postgis.

Of course, there might be some hard-coded extension version numbers in the
dump. Run "pg_dump --schema-only $DB >> ${DB}.sql" and then scan it for
postgis references to "see what you see". Maybe even run that no-data
script on the new server, and see what postgis and fk versions you get.

> Is there anyone have experience with this?
>

--
Death to America, and butter sauce.
Iraq lobster!

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Mahendra Singh 2024-08-27 15:55:08 Error while starting EFM
Previous Message hubert depesz lubaczewski 2024-08-27 11:37:09 Re: complain about closing bugreports with wrong reason