| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Greg Smith" <gsmith(at)gregsmith(dot)com> |
| Cc: | "Campbell, Lance" <lance(at)uiuc(dot)edu>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Backup causing poor performance - suggestions |
| Date: | 2008-05-05 21:50:30 |
| Message-ID: | dcc563d10805051450w6d53ccfh7ede4ada8d53efaa@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, May 5, 2008 at 2:03 PM, Greg Smith <gsmith(at)gregsmith(dot)com> wrote:
> On Mon, 5 May 2008, Campbell, Lance wrote:
>
>
> > We currently backup all of our database tables per schema using pg_dump
> > every half hour. We have been noticing that the database performance
> > has been very poor during the backup process. How can I improve the
> > performance?
> >
>
> Uh, don't do that? pg_dump works OK doing periodic backups during
> relatively calm periods, it's not really appropriate to run all the time
> like that.
Wow, my reading comprehension must be dropping. I totally missed the
every half hour bit and read it as every day. If you're backing up a
live database every hour, then yes, it's a very good idea to switch to
a hot or cold standby method with PITR
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig James | 2008-05-05 23:33:01 | RAID 10 Benchmark with different I/O schedulers (was: Performance increase with elevator=deadline) |
| Previous Message | Greg Smith | 2008-05-05 20:11:27 | Re: Backup causing poor performance - suggestions |