From: Scott Marlowe <scott.marlowe@gmail.com>
To: Greg Smith <gsmith@gregsmith.com>
Cc: Campbell, Lance <lance@uiuc.edu>
Cc: pgsql-performance@postgresql.org
Subject: Re: Backup causing poor performance - suggestions
Date: Mon, 5 May 2008 15:50:30 -0600
Message-ID: <dcc563d10805051450w6d53ccfh7ede4ada8d53efaa@mail.gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.64.0805051305320.10353@westnet.com>
References: <B10E6810AC2A2F4EA7550D072CDE8760CDDD2C@SAB-FENWICK.sab.uiuc.edu>
<Pine.GSO.4.64.0805051305320.10353@westnet.com>
On Mon, May 5, 2008 at 2:03 PM, Greg Smith <gsmith@gregsmith.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: scott.marlowe@gmail.com, gsmith@gregsmith.com, lance@uiuc.edu
Subject: Re: Backup causing poor performance - suggestions
In-Reply-To: <dcc563d10805051450w6d53ccfh7ede4ada8d53efaa@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox