Yes thank you.
I actually did get it working eventually, with the things you mentioned.
Also, the recovery.conf has to be in the directory that contains the data
folder! I previously had it in the folder with the config files, which in
my installation are different. Once I moved the recovery.conf
In your recovery.conf, you should also have a restore_command setting.
That's what the standby postgres will use to grab the archived WAL logs from
the master and it needs to. So yes, you need archive set to on and an
archive_command command setting on the master. You at least need that for
catch
On Mon, Oct 17, 2011 at 2:44 PM, Ray Stell wrote:
> On Sun, Oct 16, 2011 at 08:21:31PM +0100, Simon Riggs wrote:
>> On Fri, Oct 14, 2011 at 3:02 PM, Ray Stell wrote:
>>
>> > The tutorial here excludes an important issue:
>> > http://wiki.postgresql.org/wiki/Binary_Replication_Tutorial#Failing_Ove
On Sun, Oct 16, 2011 at 08:21:31PM +0100, Simon Riggs wrote:
> On Fri, Oct 14, 2011 at 3:02 PM, Ray Stell wrote:
>
> > The tutorial here excludes an important issue:
> > http://wiki.postgresql.org/wiki/Binary_Replication_Tutorial#Failing_Over_To_The_Standby
> > After the failover is complete, it
On Oct 14, 2011, at 12:17 PM, Devrim GÜNDÜZ wrote:
> On Fri, 2011-10-14 at 11:19 +0530, Karuna Karpe wrote:
>>
>> can any one tell me that, oracle flashback similar concept
>> in postgresql?
>
> We don't have exactly the same, but we have PITR -- the result is the
> same, but done in a
