From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "David F(dot) Skoll" <dfs(at)roaringpenguin(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Warm-standby robustness question |
Date: | 2007-12-28 16:11:16 |
Message-ID: | 20071228161116.GB7821@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Kevin Grittner wrote:
> >>> On Tue, Dec 18, 2007 at 12:55 PM, in message <3149(dot)1198004157(at)sss(dot)pgh(dot)pa(dot)us>,
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > "David F. Skoll" <dfs(at)roaringpenguin(dot)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.
But hint bits should be replicated on the next full-page-write anyhow,
no?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Usama Dar | 2007-12-28 22:40:02 | Re: Fresh copy of a PG DB ? |
Previous Message | Peter Eisentraut | 2007-12-28 15:52:45 | Re: reconfiguring diskspace while upgrading to 8.2.5 |