| From: | Geoff Montee <geoff(dot)montee(at)gmail(dot)com> |
|---|---|
| To: | Hello World <worldanizer(at)gmail(dot)com> |
| Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Security Issues: Allowing Clients to Execute SQL in the Backend. |
| Date: | 2014-04-30 11:08:53 |
| Message-ID: | CAA7biFNB_xWU3fvLxzgGNY53MSVMrpVQdtpsZ_Q7aJ78Yj_Q_A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
They don't apply server-wide. They apply to that user's session:
http://www.postgresql.org/docs/8.4/interactive/sql-set.html
Geoff
On Wed, Apr 30, 2014 at 6:19 AM, Hello World <worldanizer(at)gmail(dot)com> wrote:
>
> SET statement_timeout=0;
>> SET work_mem=1024GB;
>>
>
> I just realized about the SET command.
>
> Isn't it weird that any user can set parameters such as this that will
> apply server wide? to all future sessions?
>
> I noticed that some of the parameters can only be set by superusers, and
> some require re-start, but still. Anybody can re-configure the server.....
> ??
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2014-04-30 11:32:24 | Re: SQL query runs fine on one platform (FreeBSD), but hangs on another (Windows) |
| Previous Message | David Noel | 2014-04-30 11:08:24 | Re: SQL query runs fine on one platform (FreeBSD), but hangs on another (Windows) |