awesome. thanks for the help. Will test it out.
thanks,
Manoj
On 07/20/2012 06:57 PM, Chris Angelico wrote:
On Sat, Jul 21, 2012 at 5:28 AM, Manoj Govindassamy
wrote:
-- Anyway I can query the state of DB to know its status slave or master ??
So, that i can issue write statements only
Hi team,
I am using PG 9.1.2 and I am promoting a slave to master with the
following command.
pg_ctl promote -D /pat/to/data
Command does return back faster with code 0 ( = success). I assumed the
slave is now the master and issued write operations. But the statement
failed as the DB compla
Hi,
I have configured PG master and slave to run under synchronous replication mode
and they are mostly working fine. Except during the setup phase. Please read
thru my setup, procedure and let me know if I am doing something stupid.
PG master :
wal_level = hot_standby
max_wal_senders = 5
ways to detect Master PG's replication not working (via libpq would
be more preferable).
thanks,
Manoj
On 01/17/2012 05:04 PM, Fujii Masao wrote:
On Wed, Jan 18, 2012 at 6:37 AM, Manoj Govindassamy
wrote:
(2) We are not comfortable moving to PGPool just for automatic failback mode
on hot-s
PM, Fujii Masao wrote:
On Tue, Jan 17, 2012 at 3:51 AM, Manoj Govindassamy
wrote:
1. Transaction which was stuck right when slave going away never went
thru even after I reloaded master's config with local commit on. I do see
all new transactions on master are going thru fine, except th
anyone with PG Synchronous Replication knowledge, please help me with
your views on the below questions.
thanks,
Manoj
On 01/12/2012 10:12 AM, Manoj Govindassamy wrote:
any help on this is much appreciated.
thanks,
Manoj
On 01/11/2012 01:50 PM, Manoj Govindassamy wrote:
Hi,
I have a
any help on this is much appreciated.
thanks,
Manoj
On 01/11/2012 01:50 PM, Manoj Govindassamy wrote:
Hi,
I have a PG 9.1.2 Master <--> Slave with synchronous replication
setup. They are all working fine as expected. I do have a case where I
want to flip Master to non replicatio
Hi,
I have a PG 9.1.2 Master <--> Slave with synchronous replication setup.
They are all working fine as expected. I do have a case where I want to
flip Master to non replication mode whenever its slave is not
responding. I have set replication_timeout to 5s and whenever salve is
not respondi
