Re: 9.3 migration issue

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Stephen Davies <sdavies(at)sdc(dot)com(dot)au>, Vick Khera <vivek(at)khera(dot)org>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: 9.3 migration issue
Date: 2014-10-13 23:51:34
Message-ID: 543C6586.70507@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/13/2014 04:28 PM, Stephen Davies wrote:
> No. Just pg_dump and pg_restore/postgis_restore.pl.

Roles(users) are global to a cluster so they will not be picked up by
pg_dump. You have the options of:

1) Using pg_dumpall to dump the entire cluster into a text file

http://www.postgresql.org/docs/9.3/interactive/app-pg-dumpall.html

$ pg_dumpall > db.out

2) Or do pg_dump on the individual databases and pg_dumpall -g to get
just the global objects, which is what Vick Khera was getting at.

-g
--globals-only

Dump only global objects (roles and tablespaces), no databases.

>
> On 13/10/14 22:24, Vick Khera wrote:
>> On Mon, Oct 13, 2014 at 12:11 AM, Stephen Davies <sdavies(at)sdc(dot)com(dot)au>
>> wrote:
>>> I have fixed this by manually granting access where necessary but wonder
>>> whether the original issue is a bug or something that I have missed
>>> in the
>>> migration.
>>
>> pg_dump emits the necessary GRANTs for the tables.
>>
>> Did you use pg_dumpall --globals-only to copy over your users and
>> their settings?
>>
>>
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stephen Davies 2014-10-13 23:53:29 Re: 9.3 migration issue
Previous Message Stephen Davies 2014-10-13 23:41:17 Re: 9.3 migration issue