From: | "Charley L(dot) Tiggs" <ctiggs(at)xpressdocs(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Selective authentication? |
Date: | 2005-08-25 20:10:22 |
Message-ID: | 6436C336-8E65-496A-A417-590856708723@xpressdocs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
For information on setting up a .pgpass file:
http://www.postgresql.org/docs/8.0/static/libpq-pgpass.html
Charley
On Aug 25, 2005, at 2:31 PM, <kynn(at)panix(dot)com> <kynn(at)panix(dot)com> wrote:
>
>
> I'm setting up PostgreSQL for a small academic lab, where I work. The
> host OS is Linux (Debian). I want to allow most users to connect to
> the database without having to supply a password, but I want to have a
> special user, called dbadmin, with superuser privileges. The idea is
> that I (or whoever gets entrusted with this responsibility) would
> connect as dbadmin *only* when the task at hand required superuser
> privileges.
>
> I'd be very grateful if someone could explain to me how to set this
> up.
>
> (If there were a simple way to obviate the need to type in a password
> every time (e.g. through a suitable command in a configuration file,
> such as one can do with ${HOME}/.my.cnf), then I could just require a
> password from everyone, but I have not found out how to do this in
> PostgreSQL.)
>
> Many thanks in advance!
>
> kj
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mike G. | 2005-08-25 20:11:03 | Superuser can execute but not view function |
Previous Message | kynn | 2005-08-25 19:31:45 | Selective authentication? |