Re: Permissions - Mailing list pgsql-novice

From David G. Johnston
Subject Re: Permissions
Date
Msg-id CAKFQuwbLCcuUhYKVzmn4KZTVp4kcObf_hU3s47_-DS6PZtN+=g@mail.gmail.com
Whole thread Raw
In response to Re: Permissions  (Andre Labuschagne <technical@eduadmin.com>)
Responses Re: Permissions  (Andre Labuschagne <technical@eduadmin.com>)
Re: Permissions  (Debra Cerda <Debra.Cerda@bluetreble.com>)
List pgsql-novice
Please don't top-post

On Tue, Sep 20, 2016 at 1:04 PM, Andre Labuschagne <technical@eduadmin.com> wrote:

Would I be correct in saying then that all roles attached to the database at the source PG server will travel to the PG server that is going to mount the copy.  What I mean by copy is to just copy the physical files.  I understand the pgDump can dump the database to a sort of archive to a script.  Is that correct?

A full physical copy of the relevant files from a stopped PostgreSQL is basically making an exact backup.  When you start/restore it you get exactly what you backed up.  This generally means "everything" and not just "a database".
 

If the super user has unrestricted access to the database on the destination PG server how would the non existence of roles restrict that access?  This is not what I am understanding.  That is why I asked about revoking the super user at the source PG server.  This is what is confusing me.


You need to describe your setup better.  You either do a complete clone - in which case there is no existing super user and you get all of the original roles - or you import into an existing cluster - in which case you will have an existing super user and need to make sure that you remember to load in all of the original roles.

​David J.​

pgsql-novice by date:

Previous
From: Andre Labuschagne
Date:
Subject: Re: Permissions
Next
From: Andre Labuschagne
Date:
Subject: Re: Permissions