| From: | Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Martin Mueller <martinmueller(at)northwestern(dot)edu>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: update from 13 to16 |
| Date: | 2023-09-16 19:01:15 |
| Message-ID: | CAOtHd0DOajBNzOCt=y=-qFMWQip+g4u1E9wivL=sKtZvuFtBEA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Sep 15, 2023, 15:02 Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
> 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
>
To elaborate on this, if you want to avoid copying the data, you may want
to take a look at pg_upgrade in link mode.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-09-16 23:03:05 | Re: Can two-phase commit support LISTEN, UNLISTEN, and NOTIFY? |
| Previous Message | James Stuart | 2023-09-15 17:55:38 | Can two-phase commit support LISTEN, UNLISTEN, and NOTIFY? |