Re: Version upgrade: is restoring the postgres database needed?

2018-03-01 Thread Vick Khera
On Thu, Mar 1, 2018 at 11:51 AM, Ron Johnson wrote: > Good. What, then, have I forgotten to restore such that the "Access > privileges" are showing on my current 9.2 servers, but not on the > newly-restored 9.6.6 server? > > *Current* > postgres=# \l >

Re: Version upgrade: is restoring the postgres database needed?

2018-03-01 Thread Ron Johnson
On 03/01/2018 11:46 AM, Adrian Klaver wrote: [snip] Hmmm.  I just looked at the script, and it says: $ pg_dumpall --schema-only > globals.sql That's not good. Well it would dump the globals, but also the schema definitions for all the objects in the cluster. Though at this point we are only

Re: Version upgrade: is restoring the postgres database needed?

2018-03-01 Thread Ron Johnson
On 03/01/2018 11:28 AM, Melvin Davidson wrote: [snip] *>Hmmm.  I just looked at the script, and it says: >$ pg_dumpall --schema-only > globals.sql >That's not good. * *No that's actually correct. pg_dumpall  can and will dump the globals * *pg_dump cannot* I was invoking --schema-only and

Re: Version upgrade: is restoring the postgres database needed?

2018-03-01 Thread Adrian Klaver
On 03/01/2018 09:22 AM, Ron Johnson wrote: On 03/01/2018 11:03 AM, Melvin Davidson wrote: *Current* postgres=# \l List of databases     Name |  Owner   | Encoding | Collate   |    Ctype    | Access privileges

Re: Version upgrade: is restoring the postgres database needed?

2018-03-01 Thread Melvin Davidson
On Thu, Mar 1, 2018 at 12:22 PM, Ron Johnson wrote: > On 03/01/2018 11:03 AM, Melvin Davidson wrote: > > > > On Thu, Mar 1, 2018 at 11:51 AM, Ron Johnson > wrote: > >> On 03/01/2018 10:37 AM, Vick Khera wrote: >> >> On Thu, Mar 1, 2018 at 11:15 AM,

Re: Version upgrade: is restoring the postgres database needed?

2018-03-01 Thread Melvin Davidson
On Thu, Mar 1, 2018 at 11:51 AM, Ron Johnson wrote: > On 03/01/2018 10:37 AM, Vick Khera wrote: > > On Thu, Mar 1, 2018 at 11:15 AM, Ron Johnson > wrote: > >> No, I do: >> >> $ pg_dump -Fc PROD > PROD.pgdump >> $ pg_dump --globals-only postgres >

Re: Version upgrade: is restoring the postgres database needed?

2018-03-01 Thread Ron Johnson
On 03/01/2018 10:37 AM, Vick Khera wrote: On Thu, Mar 1, 2018 at 11:15 AM, Ron Johnson > wrote: No, I do: $ pg_dump -Fc PROD > PROD.pgdump $ pg_dump --globals-only postgres > globals.sql $ pg_dump -Fc postgres >

Re: Version upgrade: is restoring the postgres database needed?

2018-03-01 Thread Vick Khera
On Thu, Mar 1, 2018 at 11:15 AM, Ron Johnson 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

Re: Version upgrade: is restoring the postgres database needed?

2018-03-01 Thread Ron Johnson
On 03/01/2018 08:46 AM, Melvin Davidson wrote: On Thu, Mar 1, 2018 at 5:24 AM, Ron Johnson > wrote: Or do we just apply the globals.sql created by "pg_dumpall --globals-only"? (We're upgrading by restoring all databases on a

Re: Version upgrade: is restoring the postgres database needed?

2018-03-01 Thread Melvin Davidson
On Thu, Mar 1, 2018 at 5:24 AM, Ron Johnson 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

Version upgrade: is restoring the postgres database needed?

2018-03-01 Thread Ron Johnson
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.