| From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
|---|---|
| To: | Naz Gassiep <naz(at)mira(dot)net> |
| Cc: | "pgsql-general(at)postgresql(dot)org >> Postgresql" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Read/Write restriction mechanism |
| Date: | 2008-01-09 12:38:46 |
| Message-ID: | 682407E1-7FCC-45A7-810D-1F78CDDA105D@seespotcode.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jan 9, 2008, at 1:39 , Naz Gassiep wrote:
> In a PHP project I have several functions that I use for DB
> operations. I only want to allow one of them to write, all the
> others are for reading only.
> (Using DB level perms are out, as this is the function usage I'm
> trying to control, not the connections).
Um, why are DB-level permissions out? It seems like a natural fit:
your writer connects as one role while the readers connect as
another. Only grant SELECT access to the readers.
Michael Glaesemann
grzm seespotcode net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2008-01-09 12:53:06 | Re: Startup scripts - Use -m fast or smart? |
| Previous Message | Harald Armin Massa | 2008-01-09 12:04:39 | Re: count(*) and bad design was: Experiences with extensibility |