nice'ing the postgres COPY backend process to make pg_dumps run more "softly"

From: Aleksey Tsalolikhin <atsaloli(dot)tech(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: nice'ing the postgres COPY backend process to make pg_dumps run more "softly"
Date: 2012-03-19 04:06:02
Message-ID: CA+jMWodd2aDioYuyiHPbqE9APokq_GJVJgwFKrbWR3P1bcxE0Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kiriakos Georgiou 2012-03-19 05:24:52 Re: Anonymized database dumps
Previous Message Jayadevan M 2012-03-19 03:39:40 Re: How to isolate the result of SELECT's?