From: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
---|---|
To: | Postgresql General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_dump / pg_dumpall / memory issues |
Date: | 2003-04-10 06:23:22 |
Message-ID: | 200304101153.22988.shridhar_daithankar@nospam.persistent.co.in |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thursday 10 April 2003 11:14, you wrote:
> > So I'm wondering if the simple solution might be to either use a slower
> > box / network connection / throttled port on the backup box, or just
> > backup into another database since the copies into the other machine
> > probably slow things down enough to render less of a load on the server
> > being backed up.
>
> Hmmm... that might be an interesting solution. We do have a slower
> standby DB, that would be excellent for that purpose. It would be an
> added incentive too, because the standby DB would be hot after backup.
> I'm gonna give this a shot and report back. I guess we can do a
> pg_dumpall from the standby DB as soon as the main DB has finished
> backing up too!
If you have an OS that binds nice value of a process to it's I/O priority, you
can lower the priority of pg_dump so that it runs very slow, so to speak.
I believe freeBSD does this. Not sure if linux does it as well.
HTH
Shridhar
From | Date | Subject | |
---|---|---|---|
Next Message | Nigel J. Andrews | 2003-04-10 08:12:37 | Re: Casting |
Previous Message | Ericson Smith | 2003-04-10 05:44:56 | Re: pg_dump / pg_dumpall / memory issues |