From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
---|---|
To: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Version upgrade: is restoring the postgres database needed? |
Date: | 2018-03-01 14:46:58 |
Message-ID: | CANu8FizxHQrPbKriyUE-iLjsVbO0iaxQ7t3b3jOfghN5agjXqw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Mar 1, 2018 at 5:24 AM, Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> wrote:
>
> Or do we just apply the globals.sql created by "pg_dumpall --globals-only"?
>
> (We're upgrading by restoring all databases on a new server, that,
> naturally, has it's own new postgres, template0 and template1 databases.)
>
>
> Thanks
>
> --
> Angular momentum makes the world go 'round.
>
>
>is restoring the postgres database needed?
That would depend on how you did the dump. If you did a_complete pg_dumpall
(did not use -g or any other limiting flags), then all roles and databases
are contained
in the output file created. NOTE: restoring from the dumped file will
require rebuilding all indexes, because indexes are not dumped.
--
*Melvin Davidson*
*Maj. Database & Exploration Specialist*
*Universe Exploration Command – UXC*
Employment by invitation only!
From | Date | Subject | |
---|---|---|---|
Next Message | Vikas Sharma | 2018-03-01 15:23:53 | Posgresql Log: lots of parse statements |
Previous Message | Kiran Krishnamachari | 2018-03-01 14:06:38 | Custom ranking function for full text search |