| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Phoenix Kiula" <phoenix(dot)kiula(at)gmail(dot)com> |
| Cc: | "Bill Moran" <wmoran(at)collaborativefusion(dot)com>, "PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Dumping/Restoring with constraints? |
| Date: | 2008-08-27 17:41:56 |
| Message-ID: | dcc563d10808271041n5e5c4d0exedba194893a58de6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On Wed, Aug 27, 2008 at 8:40 AM, Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> wrote:
> Thanks. But there seems to be a tangible slowdown of DB operations
> during the time that pg_dump is running. Perhaps some of my
> postgresql.conf variables are not geared to this. (I vaguely recall
> setting it up so that the wal_buffers or checkpoint_segments needed to
> be set upwards for maintenance tasks).
>
> My question: is it possible to interactively set up these variables so
> that pg_dumpall can work very fast? And behind the scenes, without
> slowing stuff down?
Nope, it's not a software problem, it's a hardware problem. You're
drive subsystem can only deliver data so fast. The fix is usually
better hardware. Big RAID controller and lots of drives.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | steve | 2008-08-27 20:36:24 | Re: WAL files during a backup |
| Previous Message | Carol Walter | 2008-08-27 17:38:45 | Another permissions question |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | William Garrison | 2008-08-27 17:45:43 | Re: Do I have a corrupted database? |
| Previous Message | Steve Clark | 2008-08-27 17:21:43 | Re: 8.3.1 query plan |