Re: Disallow SET command in a postgresql server - Mailing list pgsql-general

From Fabio Rueda Carrascosa
Subject Re: Disallow SET command in a postgresql server
Date
Msg-id CAA3M-faZeDx0drj2vWDz4irKJpPRLw6y+qZPgNEpfuxqQnd8Ng@mail.gmail.com
Whole thread Raw
In response to Re: Disallow SET command in a postgresql server  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Disallow SET command in a postgresql server
Re: Disallow SET command in a postgresql server
List pgsql-general
My grant/revoke architecture is fine, you mean about costly cpu/ram queries?


2013/4/9 Tom Lane <tgl@sss.pgh.pa.us>
Fabio Rueda Carrascosa <avances123@gmail.com> writes:
> Im planning to publish my postgresql server to a few untrusted clients.
> I dont want them to modify any runtime setting, like work_mem or something
> risky to my server. In general I assume the pg_catalog schema is public but
> I don't want to allow updating pg_settings at all.

If you're allowing untrustworthy users to execute arbitrary SQL,
preventing them from using SET would not make very much difference
in how much trouble they can cause.  You're wasting your time worrying
about this.

                        regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Disallow SET command in a postgresql server
Next
From: Alvaro Herrera
Date:
Subject: Re: Disallow SET command in a postgresql server