From: | Fabio Rueda Carrascosa <avances123(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Disallow SET command in a postgresql server |
Date: | 2013-04-09 15:57:50 |
Message-ID: | CAA3M-faZeDx0drj2vWDz4irKJpPRLw6y+qZPgNEpfuxqQnd8Ng@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
My grant/revoke architecture is fine, you mean about costly cpu/ram queries?
2013/4/9 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Fabio Rueda Carrascosa <avances123(at)gmail(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2013-04-09 16:06:59 | Re: Disallow SET command in a postgresql server |
Previous Message | Tom Lane | 2013-04-09 15:47:12 | Re: Disallow SET command in a postgresql server |