Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 756122E0055 for ; Mon, 24 Mar 2008 19:49:45 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 87051-06 for ; Mon, 24 Mar 2008 19:49:42 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by postgresql.org (Postfix) with ESMTP id DADB32E0051 for ; Mon, 24 Mar 2008 19:49:41 -0300 (ADT) Received: by fg-out-1718.google.com with SMTP id 22so2967160fge.23 for ; Mon, 24 Mar 2008 15:49:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=eCAf1T/HS7ckvKD1yDp2klFac683h8lT/8zTkKNrWkA=; b=ELwkuHBEaPCZEY3BSetFBgAwhFCCue655DY2UPuIKhqKYi5ciXsSVeSjzsjBIMald/REOe9y3AV3H+GsYT+rhLiyJFPKS7G3tvFh1SCDb2fNSgK7L5RCXIDHtEKaNTVsuo28CYowBVvMj9tm/gqACaiHUgQZYoN9j3OVmeC+45A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nh6SN9J/iLmfJ5B64T++mztRXQZ0ZQOBc30DlZuePG10NPJQkV0dDZ6mFRUSaBQ/dJ+KwCtqZ8fSQMuS+1rAIlGXQC+/x8Rn8LRYIC0ojwIdLTYPOhZSQ5qNFewdgMvf1A4drzZOnIhroFz0Lw/DYKN3UGCuItBVNe4g2V1qH7I= Received: by 10.82.175.17 with SMTP id x17mr18853230bue.19.1206398980380; Mon, 24 Mar 2008 15:49:40 -0700 (PDT) Received: by 10.86.84.11 with HTTP; Mon, 24 Mar 2008 15:49:40 -0700 (PDT) Message-ID: <721b21dc0803241549y3ab1b4e7iff7cf8aec66e48d7@mail.gmail.com> Date: Mon, 24 Mar 2008 15:49:40 -0700 From: "Steve Poe" To: "Tom Lane" Subject: Re: Planning hot/live backups? Cc: "Matthew T. O'Connor" , pgsql-performance@postgresql.org In-Reply-To: <3769.1206397428@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <721b21dc0803241323u73443060w3a1912d52714549b@mail.gmail.com> <47E8128E.1060600@zeut.net> <3769.1206397428@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=AWL=0.000 X-Spam-Level: X-Archive-Number: 200803/453 X-Sequence-Number: 29407 Tom, So, are you saying we need to get to at least 8.1.x before considering PITR for a production environment? Unfortunately, the vendor/supplier of our veterinary application does not support higher versions. We would be proceeding "at our own risk". Is there anything else we can do we 8.0.15 version? Steve On Mon, Mar 24, 2008 at 3:23 PM, Tom Lane wrote: > > "Matthew T. O'Connor" writes: > > Steve Poe wrote: > >> The owners of the animal hospital where I work at want to consider live/hot > >> backups through out the day so we're less likely to lose a whole > >> day of transaction. We use Postgresql 8.0.15. We do 3AM > >> backups, using pg_dumpall, to a file when there is very little activity. > > > You probably want to look into PITR, you can have a constant ongoing > > backup of your data and never lose more than a few minutes of data. The > > overhead isn't all the big especially if you are shipping the log files > > to a separate server. > > But note that you really need to update to a newer major release before > depending on PITR. While 8.0 nominally has support for it, it's taken > us several releases to really get the operational gotchas sorted out. > > regards, tom lane >