Re: How to deal with multiple accounts

From: Michel Feinstein <michelfeinstein(at)gmail(dot)com>
To: Doug Easterbrook <doug(at)artsman(dot)com>
Cc: Michael Shapiro <mshapiro51(at)gmail(dot)com>, "pgadmin-support lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: Re: How to deal with multiple accounts
Date: 2019-05-19 05:28:43
Message-ID: CAEg4jbOGDG-4VSoFCAJ4QTe48RE6X6NvdxqH+1EK=n+ge4HvQQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

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(at)artsman(dot)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(at)artsman(dot)com <doug(at)artsman(dot)com>
> http://www.artsman.com
> Phone (403) 650-1978
>
> On May 18, 2019, at 3:19 PM, Michael Shapiro <mshapiro51(at)gmail(dot)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(at)gmail(dot)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.
>>
>
>

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Doug Easterbrook 2019-05-19 13:14:29 Re: How to deal with multiple accounts
Previous Message Doug Easterbrook 2019-05-19 03:00:30 Re: How to deal with multiple accounts