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

From Merlin Moncure
Subject Re: Disallow SET command in a postgresql server
Date
Msg-id CAHyXU0xrz3BDic2JROSv77xGfgYXWv9m0nUivhqYNO9C_abYWQ@mail.gmail.com
Whole thread Raw
In response to Re: Disallow SET command in a postgresql server  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-general
On Tue, Apr 9, 2013 at 11:13 AM, Merlin Moncure <mmoncure@gmail.com> wrote:
> On Tue, Apr 9, 2013 at 10:57 AM, Fabio Rueda Carrascosa
> <avances123@gmail.com> wrote:
>> My grant/revoke architecture is fine, you mean about costly cpu/ram queries?
>
> it has nothing to do with grant/revoke.   There are multiple trivial
> things a user can do to DOS you server.  You can prevent a lot of
> them, but it's definitely whack-a-mole.  If you don't believe me, try
> logging into schemaverse in the next few moments.  I just took it
> down.  It will come up shortly.

schemaverse (one of the neatest things on the internet) is now functioning!

merlin


pgsql-general by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Disallow SET command in a postgresql server
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Disallow SET command in a postgresql server