Re: Updated version of pg_receivexlog - Mailing list pgsql-hackers

From Ants Aasma
Subject Re: Updated version of pg_receivexlog
Date
Msg-id CA+CSw_swtpx8=d-+ew3WZR4teX8nohgJ5QFuheJm3xT=4vVG7Q@mail.gmail.com
Whole thread Raw
In response to Re: Updated version of pg_receivexlog  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Mon, Jun 4, 2012 at 6:53 PM, Magnus Hagander <magnus@hagander.net> wrote:
> No, it's more a "there's no reason to do that". I don't think it
> should necessarily be an actual problem.

Ok, good to know.

> In your case the missing piece of information is why was there a
> timeline switch? pg_basebackup shouldn't cause a timeline switch
> whether you use it in -x mode or not.

No mystery there. The timeline switch was because I had just promoted
the master for standby mode. There's a chance I might have
accidentally done something horribly wrong somewhere because I can't
immediately reproduce this. I'll let you know if I find out how I
managed to create this error.

Ants Aasma
--
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt
Web: http://www.postgresql-support.de


pgsql-hackers by date:

Previous
From: Florian Pflug
Date:
Subject: Re: [RFC] Interface of Row Level Security
Next
From: Greg Sabino Mullane
Date:
Subject: Btree or not btree? That is the question