Re: update from 13 to16

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Martin Mueller <martinmueller(at)northwestern(dot)edu>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: update from 13 to16
Date: 2023-09-15 17:01:06
Message-ID: 82a1d5a5-1ddd-260e-5b25-9b30d127c66c@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On 9/15/23 9:55 AM, Martin Mueller wrote:
>
> I am thinking of upgrading from version 13 to version 16.
>
> I think I can do this by leaving the data alone and just replacing the
> software.  My data are extremely simple and consist of several hundred
>
No you can't.

You will need to either use pg_upgrade:

https://www.postgresql.org/docs/16/pgupgrade.html

or do dump/restore using some combination of:

https://www.postgresql.org/docs/16/app-pgdump.html

https://www.postgresql.org/docs/16/app-pg-dumpall.html

and

https://www.postgresql.org/docs/16/app-pgrestore.html

https://www.postgresql.org/docs/16/app-psql.html

>  tables, some with close to ten million records.  But their structure
> is simple.  I access the data via Aqua Data Studio, as if they were
> very large spreadsheets.
>
> Is that a correct analysis?  I just want to make sure.
>
> Martin Mueller
>
> Professor  emeritus of English and Classsics
>
> Northwestern University
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message James Stuart 2023-09-15 17:55:38 Can two-phase commit support LISTEN, UNLISTEN, and NOTIFY?
Previous Message Martin Mueller 2023-09-15 16:55:59 update from 13 to16