From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Sebastian P(dot) Luque" <spluque(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: authentication/privileges |
Date: | 2013-05-10 16:32:07 |
Message-ID: | 20130510163207.GB17166@eldon.alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane escribió:
> It's fairly common for distro-supplied packages to create a postgres
> OS user but not assign it any password. In that state, the only way to
> become postgres is to "su" to it from root, or perhaps from a sudoer
> account with root-equivalent privileges. While that might be okay
> for machines with just one person administering everything, I can't
> say that I think it's recommendable practice in general: you don't
> want to have to give somebody root to let them admin the database.
> Better to give the postgres user a password.
Of course, it's also possible to give multiple people sudo-to-postgres
capability without giving them sudo-to-root.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Evan D. Hoffman | 2013-05-10 16:34:36 | Re: Deploying PostgreSQL on CentOS with SSD and Hardware RAID |
Previous Message | Merlin Moncure | 2013-05-10 16:25:35 | Re: Deploying PostgreSQL on CentOS with SSD and Hardware RAID |