From: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
---|---|
To: | CS_DBA <cs_dba(at)consistentstate(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: HOT standby on windows not working |
Date: | 2014-04-11 00:28:08 |
Message-ID: | CAJrrPGf7VtxNpH52uFx6m9m9jwGfnMkE3r1RtQKgUTwFZbvUyA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Apr 11, 2014 at 8:15 AM, CS_DBA <cs_dba(at)consistentstate(dot)com> wrote:
> Hi All;
>
> We're setting up a HOT standby on Windows 2000 server and PostgreSQL 9.2
>
> We do this:
> I've also tried this approach:
>
>
> 1) Master postgresql.conf file
> Modify the following settings:
> listen_address = '*'
> wal_level = hot_standby
> max_wal_senders = 3
>
>
> 2) Modify Master pg_hba.conf file:
> hostssl replication al 192.168.91.136/32 trust
>
> 3) RESTART MASTER DATABASE
Use the pg_basebackup utility to take the backup directory and change
the the conf files.
> 4) Slave postgresql.conf file
> hot_standby = on
>
> 5) Create a recovery.conf file on the slave as follows:
> standby_mode = 'on'
> primary_conninfo = 'host=192.168.91.165'
>
> 6) start the standby database
Try with the above approach.
Regards,
Hari Babu
Fujitsu Australia
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2014-04-11 00:45:52 | Re: [GENERAL] About upgrading a (tuple?) lock in a rollback'd sub-transaction |
Previous Message | Steve Crawford | 2014-04-10 23:40:44 | Re: openssl heartbleed |