| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Philip Warner'" <pjw(at)rhyme(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Cc: | brianb-pggeneral(at)edsamail(dot)com |
| Subject: | AW: pg_dump & performance degradation |
| Date: | 2000-08-07 13:32:45 |
| Message-ID: | 11C1E6749A55D411A9670001FA687963368041@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2000-08-07 13:50:20 | AW: Now PostgreSQL recovers from errors within trns |
| Previous Message | Zeugswetter Andreas SB | 2000-08-07 13:23:11 | AW: Questionable coding in proc.c & lock.c |