nice comes to mind:

nice pg_dump ...



On Sat, 2005-10-22 at 07:39, Bryan Field-Elliot wrote:
> We have a huge database which must be backed up
every day with
> pg_dump. The problem is, it takes around half an
hour to produce the
> dump file, and all other processes on the same box
are starved for
> cycles (presumably due to I/O) during the dump. It's
not just an
> inconvenience, it's now evolved into a serious
problem that needs to
> be addressed.
>
> Is there any mechanism for running pg_dump with a
lower priority? I
> don't mind if the backup takes two hours instead of
half an hour, as
> long as other processes were getting their fair
share of cycles.



__________________________________
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

On 10/24/05, CSN <cool_screen_name90001@yahoo.com> wrote:
>
> nice comes to mind:
>
> nice pg_dump ...
>

as mentioned earlier...nice isn't going to do anything for I/O. PITR
(point in time recovery) would be, in my opinion, the best solution to
this problem.

aaron.glenn

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly