Re: Time limit for a process to hold Content lock in Buffer Cache - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Time limit for a process to hold Content lock in Buffer Cache
Date
Msg-id 15879.1369321261@sss.pgh.pa.us
Whole thread Raw
In response to Re: Time limit for a process to hold Content lock in Buffer Cache  (Atri Sharma <atri.jiit@gmail.com>)
Responses Re: Time limit for a process to hold Content lock in Buffer Cache
Re: Time limit for a process to hold Content lock in Buffer Cache
List pgsql-hackers
Atri Sharma <atri.jiit@gmail.com> writes:
> BTW, what is your opinion on a rogue client's damaging capabilities?
> Theoretically, what can a client which tries to stall the backend
> target?

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.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Atri Sharma
Date:
Subject: Re: Time limit for a process to hold Content lock in Buffer Cache
Next
From: Atri Sharma
Date:
Subject: Re: Time limit for a process to hold Content lock in Buffer Cache