| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Maria(dot)L(dot)Wilson-1(at)nasa(dot)gov |
| Cc: | "Plugge, Joe R(dot)" <JRPlugge(at)west(dot)com>, "Wilson, Maria Louise (LARC-E301)[SCIENCE SYSTEMS APPLICATIONS]" <m(dot)l(dot)wilson(at)nasa(dot)gov>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: postgres database user account |
| Date: | 2010-06-30 20:16:43 |
| Message-ID: | 16427.1277929003@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Maria L. Wilson" <Maria(dot)L(dot)Wilson-1(at)nasa(dot)gov> writes:
> so what about the operating system account that is different? What we
> are planning on doing with the OS acct (postgres) is only allowing users
> sudo ability to this account. Nobody should be able to directly log
> into it. Do you think that will cause problems?
No, that's pretty standard. RPM installations for example have never
assigned a password to the postgres OS account, so it will behave in
exactly that way.
Usually the only things you need the OS account for are to start/stop
the server and update its outside-the-database configuration files,
such as postgresql.conf.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-06-30 20:30:15 | Re: cache lookup failed for index |
| Previous Message | Maria L. Wilson | 2010-06-30 20:15:44 | Re: postgres database user account |