From: Denis Lussier <denisl@enterprisedb.com>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: George Pavlov <gpavlov@mynewplace.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PITR performance overhead?
Date: Thu, 3 Aug 2006 01:21:56 -0400
Message-ID: <5f820f750608022221s69e6d593oa9778a759a625bc4@mail.gmail.com> (raw)
In-Reply-To: <b42b73150608011817s67612f90n6c7940868fc6082b@mail.gmail.com>
References: <20060731170833.GH2900@mathom.us>
<8C5B026B51B6854CBE88121DBF097A863329F2@ehost010-33.exch010.intermedia.net>
<b42b73150608011817s67612f90n6c7940868fc6082b@mail.gmail.com>
If your server is heavily I/O bound AND you care about your data AND your
are throwing out your WAL files in the middle of the day... You are headed
for a cliff.
I'm sure this doesn't apply to anyone on this thread, just a general
reminder to all you DBA's out there who sometimes are too busy to implement
PITR until after a disaster strikes. I know that in the past I've
personally been guilty of this on several occasions.
--Denis
EnterpriseDB (yeah, rah, rah...)
On 8/1/06, Merlin Moncure <mmoncure@gmail.com> wrote:
>
> On 8/1/06, George Pavlov <gpavlov@mynewplace.com> wrote:
> > I am looking for some general guidelines on what is the performance
> > overhead of enabling point-in-time recovery (archive_command config) on
> > an 8.1 database. Obviously it will depend on a multitude of factors, but
> > some broad-brush statements and/or anecdotal evidence will suffice.
> > Should one worry about its performance implications? Also, what can one
> > do to mitigate it?
>
> pitr is extremely cheap both in performance drag and administation
> overhead for the benefits it provides. it comes almost for free, just
> make sure you can handle all the wal files and do sane backup
> scheduling. in fact, pitr can actually reduce the load on a server
> due to running less frequent backups. if your server is heavy i/o
> loaded, it might take a bit of planning.
>
> merlin
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
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: denisl@enterprisedb.com, mmoncure@gmail.com, gpavlov@mynewplace.com
Subject: Re: PITR performance overhead?
In-Reply-To: <5f820f750608022221s69e6d593oa9778a759a625bc4@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