From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
---|---|
To: | Shoaib Mir <shoaibmir(at)gmail(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: shared folder in Hot Standby |
Date: | 2011-04-04 06:20:38 |
Message-ID: | BANLkTinTNdzdo47YqEm7j_TaP8_htJY6Tg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Apr 4, 2011 at 12:35 AM, Shoaib Mir <shoaibmir(at)gmail(dot)com> wrote:
> From my limited knowledge I think we need a shared location where the master
> node is putting the WAL files in and the slave nodes also look at the same
> folder to get new WAL logs to replay the files. Now if we cant have that
> shared location and a scenario where all slaves and the master cant see one
> shared location, how to approach this?
no. while you can do that, it's optional...
you can setup a hot standby just by setting:
on master:
=== postgresql.conf ===
wal_level=hot_standby
archive_mode=on
archive_command='exit 0'
max_wal_senders = <number of slaves or greater>
on slave:
=== postgresql.conf ===
hot_standby=on
=== recovery.conf ===
standby_mode='on'
primary_conninfo = 'host=master_ip'
or you can use repmgr to make all this easier:
http://projects.2ndquadrant.com/repmgr
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Harald Armin Massa | 2011-04-04 08:47:42 | PostgreSQL documentation on kindle - best practices? |
Previous Message | Shoaib Mir | 2011-04-04 05:35:34 | shared folder in Hot Standby |