Re: Backup history file should be replicated in Streaming Replication?

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Backup history file should be replicated in Streaming Replication?
Date: 2009-12-30 17:24:21
Message-ID: 1262193861.19367.5726.camel@ebony
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2009-12-30 at 15:31 +0200, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> > The code has always been capable of starting without this, which was
> > considered a feature to be able start from a hot copy.
>
> Why is that desirable? The system is in an inconsistent state. To force
> it, you can always use pg_resetxlog.

It's not desirable, for me, but its been there since 8.0 and I have no
info on whether its used. If you have a workaround that allows us to
continue to support it, I suggest you document it and then plug the gap
as originally suggested by you.

--
Simon Riggs www.2ndQuadrant.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2009-12-30 17:38:53 Re: PATCH: Add hstore_to_json()
Previous Message Robert Haas 2009-12-30 17:16:41 Re: KNNGiST for knn-search (WIP)