From: | Kiriakos Georgiou <kg-f6a3c(at)mockbites(dot)com> |
---|---|
To: | Aleksey Tsalolikhin <atsaloli(dot)tech(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: nice'ing the postgres COPY backend process to make pg_dumps run more "softly" |
Date: | 2012-03-19 06:09:53 |
Message-ID: | 6BD41B3C-FAE3-4639-A5CD-C315F7878314@mockbites.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
From | Date | Subject | |
---|---|---|---|
Next Message | Janning Vygen | 2012-03-19 08:09:49 | Re: Anonymized database dumps |
Previous Message | Kiriakos Georgiou | 2012-03-19 05:47:31 | Re: How to isolate the result of SELECT's? |