pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: David F. Skoll <dfs@roaringpenguin.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Warm-standby robustness question
Date: Fri, 28 Dec 2007 09:37:46 -0600
Message-ID: <4774C3EA.EE98.0025.0@wicourts.gov> (raw)
In-Reply-To: <3149.1198004157@sss.pgh.pa.us>
References: <4768081F.90500@roaringpenguin.com>
	<4768081F.90500@roaringpenguin.com>
	<3149.1198004157@sss.pgh.pa.us>

>>> On Tue, Dec 18, 2007 at 12:55 PM, in message <3149.1198004157@sss.pgh.pa.us>,
Tom Lane <tgl@sss.pgh.pa.us> wrote: 
> "David F. Skoll" <dfs@roaringpenguin.com> writes:
>> My question is this:  If the master database is fairly busy, gets
>> VACUUMed once a day, etc. can we expect the warm standby server
>> to work correctly after days/weeks/months/years of log shipping,
>> or should we periodically take new base backups?
> 
> I don't think the time period is at issue.  Log-shipping should keep the
> slave a perfect replica of the master (if it doesn't, we have problems
> anyway).
 
Except for hint bits.  This becomes more of a post-recovery
performance issue as the base backup ages, since they are included
in base backups, but not in WAL files.
 
http://archives.postgresql.org/pgsql-performance/2007-12/msg00203.php
 
> The operational question you need to ask yourself is: if
> you haven't swapped to the slave lately, how do you know it will work
> when you need it to?
 
Absolutely.  Nobody should ever assume they have a working backup
system without periodic tests that the backups can actually be used
to create a working system.  Ever.
 
-Kevin
 





view thread (4+ messages)  latest in thread

Message-ID: <4774C3EA.EE98.0025.0@wicourts.gov>
Permalink:  ../4774C3EA.EE98.0025.0@wicourts.gov/
Also on:    postgresql.org/message-id/4774C3EA.EE98.0025.0@wicourts.gov

 · 

reply

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-admin@postgresql.org
  Cc: Kevin.Grittner@wicourts.gov, dfs@roaringpenguin.com, tgl@sss.pgh.pa.us
  Subject: Re: Warm-standby robustness question
  In-Reply-To: <4774C3EA.EE98.0025.0@wicourts.gov>

* 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