Re: PG9.1 migration to PG9.6, dump/restore issues

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scot Kreienkamp <Scot(dot)Kreienkamp(at)la-z-boy(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: PG9.1 migration to PG9.6, dump/restore issues
Date: 2018-09-12 14:39:35
Message-ID: 3002.1536763175@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Scot Kreienkamp <Scot(dot)Kreienkamp(at)la-z-boy(dot)com> writes:
> Restore completes successfully, but I noticed that the schema
> permissions are missing, possibly others as well (Is this a known
> issue?).

If you're talking about custom modifications you made to the permissions
of the "public" schema in particular, then yeah, that won't be tracked
(IIRC, it will be with newer source server versions, but not 9.1).
Otherwise, no, that's not expected. Would you provide more detail?

> These are the commands I'm using now:
> pg_dump -sh $OLDSERVER $DATABASE -f $BACKUPPATH/$DATABASE.schema.sql
> pg_dump -vj 4 -F d -h $OLDSERVER $DATABASE -f $BACKUPPATH/DATABASE --no-synchronized-snapshots
> createdb $DATABASE
> psql -d $DATABASE -f $BACKUPPATH/$DATABASE.schema.sql
> pg_restore -evj 4 -d $DATABASE $BACKUPPATH/$DATABASE -a --disable-triggers

Also note that this recipe does not copy "global" objects (users and
tablespaces), nor does it restore any database-level properties.
You'd need to use pg_dumpall to transfer those things automatically.
(Possibly "pg_dumpall -g" would be a good starting point here.)

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2018-09-12 14:40:19 Re: PG9.1 migration to PG9.6, dump/restore issues
Previous Message Adrian Klaver 2018-09-12 14:09:38 Re: PG9.1 migration to PG9.6, dump/restore issues