Re: pg_upgrade: can I use same binary for old & new? - Mailing list pgsql-general

From Tom Lane
Subject Re: pg_upgrade: can I use same binary for old & new?
Date
Msg-id 70968.1751743653@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_upgrade: can I use same binary for old & new?  (Pierre Fortin <pf@pfortin.com>)
List pgsql-general
Pierre Fortin <pf@pfortin.com> writes:
> OK...  I failed to mention I have several databases in this cluster; so
> digging into pg_dumpall, I see:
>    --binary-upgrade
>     This option is for use by in-place upgrade utilities. Its use for
>     other purposes is not recommended or supported. The behavior of the
>     option may change in future releases without notice.

That is infrastructure for pg_upgrade to use.  Do not try to use it
manually; it won't end well.

> All my DBs are static (only queries once loaded). Assuming the dumpall
> file fits on one of my drives:
>  pg_dumpall -f <path>/PG.backup -v 
> appears to be all I need? pg_dump has compression by default; but I don't
> see compression with dumpall other than for TOAST.

I would try that first before messing with compression.  If it doesn't
fit, you'll need to do pg_dumpall --globals-only (mainly to capture
your role definitions) and then pg_dump each database into a separate
compressed file.

            regards, tom lane



pgsql-general by date:

Previous
From: Pierre Fortin
Date:
Subject: Re: pg_upgrade: can I use same binary for old & new?
Next
From: Ron Johnson
Date:
Subject: Re: pg_upgrade: can I use same binary for old & new?