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
I pretty much didn't change anything in the config files except what was in
the tutorial at http://wiki.postgresql.org/wiki/Binary_Replication_Tutorial
on the slave I created a recovery.conf file containing:
standby_mode = 'on'
primary_conninfo = 'host='
on the master postgresql.conf I set
listen
Do not rsync the pg_xlog. Basically that error means that the
restore_command in your recovery.conf is not working. You have hot_standby
archiving going on the master and a recovery_command on the slave, right?
On Thu, Oct 13, 2011 at 10:41 AM, Evan Walter
wrote:
>
>
> Hello,
> I am somewhat n
Yes, sorry. Type
Evan
On Thu, Oct 13, 2011 at 12:20 PM, Scott Marlowe wrote:
> On Thu, Oct 13, 2011 at 9:41 AM, Evan Walter
> wrote:
> >
> >
> > Hello,
> > I am somewhat new with postgresql trying to find a good method of
> > replication for my company.
> > I am running through the tutorials o
On Thu, Oct 13, 2011 at 9:41 AM, Evan Walter
wrote:
>
>
> Hello,
> I am somewhat new with postgresql trying to find a good method of
> replication for my company.
> I am running through the tutorials on binary replication for postgresql
> 9.1. Both servers are virtual box Ubuntu 10.10 on a laptop
