On Mon, Mar 19, 2012 at 3:51 PM, Guillaume Lelarge
wrote:
> On Sun, 2012-03-18 at 21:06 -0700, Aleksey Tsalolikhin wrote:
>> Hi. When pg_dump runs, our application becomes inoperative (too
>> slow). I was going to ask if nice'ing the postgres backend process
>> that handles the COPY would help b
On 03/19/2012 01:51 PM, Guillaume Lelarge wrote:
On Sun, 2012-03-18 at 21:06 -0700, Aleksey Tsalolikhin wrote:
Hi. When pg_dump runs, our application becomes inoperative (too
slow)
Depends on what your app is doing. It doesn't block any usual use of the
database: DML are all accepted. But
On Sun, 2012-03-18 at 21:06 -0700, Aleksey Tsalolikhin wrote:
> Hi. When pg_dump runs, our application becomes inoperative (too
> slow). I was going to ask if nice'ing the postgres backend process
> that handles the COPY would help but I just realized probably the
> pg_dump takes out locks when i
Try this: http://klicman.org/throttle/
Kiriakos
On Mar 19, 2012, at 12:06 AM, Aleksey Tsalolikhin wrote:
> Hi. When pg_dump runs, our application becomes inoperative (too
> slow). I was going to ask if nice'ing the postgres backend process
> that handles the COPY would help but I just reali
Hi. When pg_dump runs, our application becomes inoperative (too
slow). I was going to ask if nice'ing the postgres backend process
that handles the COPY would help but I just realized probably the
pg_dump takes out locks when it runs and nice'ing it would just make
it run longer...
However the m
