AW: pg_dump & performance degradation - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: pg_dump & performance degradation
Date
Msg-id 11C1E6749A55D411A9670001FA687963368041@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
List pgsql-hackers
> Brian Baquiran in the [GENERAL] list recently asked if it was 
> possible to
> 'throttle-down' pg_dump so that it did not cause an IO bottleneck when
> copying large tables.
> 
> Can anyone see a reason not to pause periodically?

How about a simple renice ? (You mention that CPU goes to 100 % too)

> 
> The only problem I have with pausing is that pg_dump runs in a single
> transaction, and I have an aversion to keeping TX's open too 
> long, but this
> is born of experience with other databases, and may not be 
> relevant to PG.

Probably not an issue with postgres.

Andreas


pgsql-hackers by date:

Previous
From: Zeugswetter Andreas SB
Date:
Subject: AW: Questionable coding in proc.c & lock.c
Next
From: Zeugswetter Andreas SB
Date:
Subject: AW: Now PostgreSQL recovers from errors within trns