Re: Version upgrade: is restoring the postgres database needed?
Vick Khera <vivek@khera.org>
From: Vick Khera <vivek@khera.org>
To: pgsql-general@lists.postgresql.org
Date: 2018-03-01T16:37:56Z
Lists: pgsql-general
On Thu, Mar 1, 2018 at 11:15 AM, Ron Johnson <ron.l.johnson@cox.net> wrote: > No, I do: > > $ pg_dump -Fc PROD > PROD.pgdump > $ pg_dump --globals-only postgres > globals.sql > $ pg_dump -Fc postgres > postgres.pgdump > > That's how I back them up as well. You are correct that all you need to do is restore the globals.sql, then each "pgdump" file individually. Just ignore the warning when it tries to restore your initial postgres superuser, since it was created by the initdb already. You probably don't need the "postgres" db at all, since it is just there to allow the client to connect to something on initial install. Normally you don't use it in production.
Commits
-
Move handling of database properties from pg_dumpall into pg_dump.
- b3f8401205af 11.0 cited