Re: nice'ing the postgres COPY backend process to make pg_dumps run more "softly" - Mailing list pgsql-general

From Kiriakos Georgiou
Subject Re: nice'ing the postgres COPY backend process to make pg_dumps run more "softly"
Date
Msg-id 6BD41B3C-FAE3-4639-A5CD-C315F7878314@mockbites.com
Whole thread Raw
In response to nice'ing the postgres COPY backend process to make pg_dumps run more "softly"  (Aleksey Tsalolikhin <atsaloli.tech@gmail.com>)
List pgsql-general
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 realized probably the
> pg_dump takes out locks when it runs and nice'ing it would just make
> it run longer...
>
> However the man page says "pg_dump does not block other users
> accessing the database  (readers  or writers)."  But if we run a
> pg_dump, the phone starts ringing, users are complaining that the web
> app is not working.
>
> Would appreciate some pointer to help me reconcile these two
> apparently contradictory facts.
>
> Best,
> -at
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general


pgsql-general by date:

Previous
From: Kevin Goess
Date:
Subject: Re: WHERE IN (subselect) versus WHERE IN (1,2,3,)
Next
From: Bill Moran
Date:
Subject: Re: Anonymized database dumps