X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 969E69FB292 for ; Thu, 3 Aug 2006 02:22:38 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 29213-09 for ; Thu, 3 Aug 2006 02:22:28 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by postgresql.org (Postfix) with ESMTP id C040E9FA48E for ; Thu, 3 Aug 2006 02:22:29 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id b36so361583pyb for ; Wed, 02 Aug 2006 22:22:27 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=TeHScmsSkf0tEVjCkFssBcLM5/4M5njldi+O92ZiYRAV7xyZE6S+L4UXvdRr3bQ7Q301IubzckcmZaewZFbkpMUPJLWeOgl5Jl66TCIRA8Bp5srwdXGSwkxdv5DW6VCTXHFQJt2BV2DCkk7SRPNomg3BHfetBbIS/70JX7XRj/k= Received: by 10.65.59.20 with SMTP id m20mr2606721qbk; Wed, 02 Aug 2006 22:22:26 -0700 (PDT) Received: by 10.64.179.18 with HTTP; Wed, 2 Aug 2006 22:21:56 -0700 (PDT) Message-ID: <5f820f750608022221s69e6d593oa9778a759a625bc4@mail.gmail.com> Date: Thu, 3 Aug 2006 01:21:56 -0400 From: "Denis Lussier" To: "Merlin Moncure" Subject: Re: PITR performance overhead? Cc: "George Pavlov" , pgsql-performance@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_67428_14286649.1154582516665" References: <20060731170833.GH2900@mathom.us> <8C5B026B51B6854CBE88121DBF097A863329F2@ehost010-33.exch010.intermedia.net> X-Google-Sender-Auth: c8141ec67f412ffa X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.383 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, HTML_MESSAGE, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/36 X-Sequence-Number: 20221 ------=_Part_67428_14286649.1154582516665 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 wrote: > > On 8/1/06, George Pavlov 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 > ------=_Part_67428_14286649.1154582516665 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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

------=_Part_67428_14286649.1154582516665--