| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Abhishek Sharma G *EXTERN*" <abhishek(dot)g(dot)sharma(at)ericsson(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Starting Postgres : user from same group |
| Date: | 2013-01-18 09:47:00 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B0579B041@ntex2010a.host.magwien.gv.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Abhishek Sharma G wrote:
> As per the Postgres design, only the user who is owner of the Postgres's Cluster Directory ( which has
> permission 700 ) can own the Postgres daemon process.
> But I have a requirement so that any other user belonging to the same group can also start the
> Postgres daemon. It might not be very difficult to change the code for this use case ( at least it
> seems to be ),
> But could some one please suggest me whether this is advisable or I will be messing up with the design
> ( I am in particular worried about the shared memory ) .
That's not really a question for the hackers list.
I'd say you set the SETUID bit on the postgres executable and make sure
that only the right people can execute it.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit kapila | 2013-01-18 10:05:26 | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
| Previous Message | Heikki Linnakangas | 2013-01-18 09:26:50 | Re: How to hack the storage component? |