>
> If you let an uncooperative user issue arbitrary SQL queries, he can
> do any number of things to put server performance into the tank.
> For instance, take out exclusive locks on all your tables and just
> go to sleep (although I think this is limited by table permissions in
> recent PG versions). Or start up an unconstrained join on some giant
> tables. etc. etc. This isn't an area that people have felt deserved
> adding a lot of overhead to control.
In such a case, would statement_timeout apply? If using
statement_timeout, would the longest a client can stall server be
limited to statement_timeout amount of time?
--
Amit Langote
