Re: Avoiding timeline generation

From: Daniel Farina <daniel(at)heroku(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Avoiding timeline generation
Date: 2011-03-25 07:57:03
Message-ID: AANLkTiko6XD1jWFqJEM25wKu4aEkcxAKk4LmU6Vwrmp-@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 25, 2011 at 12:38 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> On 25.03.2011 03:00, Daniel Farina wrote:
>>
>> Here is the mechanism:  I want to author a recovery.conf to perform
>> some amount of restore_command or streaming replication based
>> recovery, but I do *not* want to generate a new timeline.  Rather, I
>> want to stay in hot standby mode to allow read-only connections.
>
> That's exactly what the standby mode is for. Add "standby_mode=on" to
> recovery.conf, and the server will do exactly that.
>
> Perhaps the documentation is not clear on this. Any suggestions on how to
> improve that?

I was actually pretty well aware of this option, if that is the case,
I fat-fingered something or had a thinko (mental bit flip?) and then
what I thought I knew about standby_mode=on was invalidated (perhaps
incorrectly). I will confirm tomorrow.

--
fdr

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2011-03-25 08:00:50 Re: Pre-set Hint bits/VACUUM FREEZE on data load..?
Previous Message Heikki Linnakangas 2011-03-25 07:51:43 Re: Pre-set Hint bits/VACUUM FREEZE on data load..?