Re: Version upgrade: is restoring the postgres database needed? - Mailing list pgsql-general

From Vick Khera
Subject Re: Version upgrade: is restoring the postgres database needed?
Date
Msg-id CALd+dcfKfqru3Nyetr3ocDuznOivahnzREX0niHw_U11WJ6HMQ@mail.gmail.com
Whole thread Raw
In response to Re: Version upgrade: is restoring the postgres database needed?  (Ron Johnson <ron.l.johnson@cox.net>)
List 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. 

pgsql-general by date:

Previous
From: Steven Lembark
Date:
Subject: Re: Enforce primary key on every table during dev?
Next
From: Alban Hertroys
Date:
Subject: Re: Enforce primary key on every table during dev?