Re: How to deal with multiple accounts - Mailing list pgadmin-support

Hi,

For inspiration...

We have/use a lot of clusters and databases in PGadmin. In PGadmin (the users
view) it is organised by product (servergroups:

server-group-product01
- server-test-database (cluster01)
- server-pre-production (cluster02)
- server-production (cluster03)

server-group-product02
- server-test-database (cluster01)
- server-pre-production (etc)
- server-production

etc

In our clusters we have different roles for typical use cases:

- test-role-read-only
- test-role-read-write
- pre-production-read-only
- ..
etc

Our users are grantet connect and a role depending of there needs. The DBA that
creates the user are giving the user an initialy password.

The products are organized by maintenance groups. A products production
databases are placed in clusters that have the same type of service windows.

We have +100 databases and people seems to we happy - as a DBA I am :-)

Best

/Jan

søn, 19 05 2019 kl. 06:14 -0700, skrev Doug Easterbrook:
> the setup with no password?
> 
> what I mean by that is when adding in the server you are required to put in a
> user and a password and there is a little checkbox about ’saving password’.  
>    we don’t save password, so the user is prompted to enter it for each
> pgadmin connection.
> 
> 
> if all the databases are in the same cluster, then use of server groups and
> servers will do nothing for you, since all the databases in the server are
> listed based on the server instance you connect to.
> 
> 
> I have not attempted to manage a bunch of databases with different
> roles/owners within a single server since we kind of figure that if you are a
> DBA .. then you are probably using pgadmin as an administration tool.
> 
> if you are looking for a user query tool and using pgadmin for that, then I
> might create different server instances.
> 
> postgres is great .. the one thing that it does slightly different is that
> users and roles CAN cross multiple databases.
> 
> if you really want segmentation between development and production, creating
> two different servers might be best.
> 
> 
> 
> Doug Easterbrook
> Arts Management Systems Ltd.
> mailto:doug@artsman.com
> http://www.artsman.com
> Phone (403) 650-1978
> 
> > On May 18, 2019, at 10:28 PM, Michel Feinstein <michelfeinstein@gmail.com>
> > wrote:
> > 
> > Ok, just to be clear then... I have one server (an AWS RDS instance, I think
> > "cluster" would be the right postgresql term), running one database, with
> > multiple roles and users inside it.
> > 
> > I am curious about your setup with no password, isn't this insecure? 
> > 
> > I am used to have several saved connections on MySQL Workbench, one for each
> > role and database (cluster) type. For example:
> > 
> > - Development Database with administrator privileges. 
> > - Development Database with user privileges. 
> > - Production Database with administrator privileges. 
> > - Production Database with user privileges. 
> > 
> > Whereas Production and Development are completely separate instances
> > (cluster, database, RDS, whatever people call them these days). 
> > 
> > So inside pgAdmin, should I create a new "server" for each one of
> > these, under the same database type "server group"? 
> > 
> > On Sun, May 19, 2019, 00:00 Doug Easterbrook <doug@artsman.com> wrote:
> > > if by ’server’, you mean a new instance of pgadmin talking to a database
> > > ..   no,.  you  can get away with one copy of pgadmin talking to multiple
> > > databases.
> > > 
> > > 
> > > if by server, you mean you open pgadmin, create a new server group, you
> > > don’t need to do that either.     Since server groups can be called
> > > whatever you want, you could use server groups, I suppose, to define
> > > people so that there is a list of people. …     mostly we use them for
> > > location — to group the various physical servers or locations that we go
> > > to.
> > > 
> > > 
> > > if by server, you mean database —   it makes it easier on users it you
> > > make a new database with their user id in it and no password.   You can
> > > also name the server with the person’s name or function so thats its
> > > easier to identify which they should pick
> > > 
> > > 
> > > but there is no getting around just double licking on a single server and
> > > entering a username/password — its just the way pgadmin seems to have been
> > > designed for eons.
> > > 
> > > 
> > > personally, I like that it saves my user id — and I supply the password..
> > > 
> > > 
> > > thats how we use it.
> > > 
> > > 
> > > Doug Easterbrook
> > > Arts Management Systems Ltd.
> > > mailto:doug@artsman.com
> > > http://www.artsman.com
> > > Phone (403) 650-1978
> > > 
> > > > On May 18, 2019, at 3:19 PM, Michael Shapiro <mshapiro51@gmail.com>
> > > > wrote:
> > > > 
> > > > I'd like to know how people do this as well. I have been creating new
> > > > Servers for each account.
> > > > 
> > > > On Sat, May 18, 2019 at 5:16 PM Michel Feinstein <
> > > > michelfeinstein@gmail.com> wrote:
> > > > > Hi guys, I am looking for opinions on how you use pgAdmin for dealing
> > > > > with several accounts.
> > > > > 
> > > > > For example, I have an "admin" account with all the privileges for the
> > > > > database and a "restricted" account for my application to use. I also
> > > > > have some other accounts for other purposes and I was looking for a
> > > > > convenient way to log into those accounts and use pgAdmin with their
> > > > > privileges.
> > > > > 
> > > > > In MySQL Workbench this was fairly simple, since you configure
> > > > > Connections, but in pgAdmin you configure Servers instead, and all
> > > > > those accounts are new connections to the same Server.
> > > > > 
> > > > > So do you guys just create a new Server for each account/login on
> > > > > pgAdmin, or do you have some other trick on how to deal this this?
> > > > > 
> > > > > Best wishes,
> > > > > 
> > > > > Michel.
> 
>