I'm not sure if is a correct approach to write at branch node, but makes sense for my use case:
I have an local instance that is my master and a web instance that is the queue consumer, which should be able to write rows that don't need to be replicated to anyone. All conflicts are already treated on application logic layer.
I have the replication configured and working, but when I write at branch node i get the following message:
ERROR: Insert into queue disallowed
CONTEXT: PL/pgSQL function pgq.insert_event(text,text,text,text,text,text,text) line 24 at RETURN
SQL statement "select pgq.insert_event($1, $2, $3, $4, $5, $6, $7)"
Seems an expected behavior, however I didn't expect that branch node would try to insert something into queue.
Shouldn't this be optional for a branch or leaf node?
master.ini
[londiste3]
db = user=postgres host=127.0.0.1 dbname=postgres
queue_name = myappq
loop_delay = 0.5
logfile = log/master.log
pidfile = pid/master.pid
slave.ini
[londiste3]
db = user=postgres host=127.0.0.1 dbname=londiste
queue_name = myappq
loop_delay = 0.5
logfile = log/slave.log
pidfile = pid/slave.pid
ticker.ini
[pgqd]
base_connstr = user=postgres host=127.0.0.1
database_list = postgres
logfile = log/ticker.log
pidfile = pid/ticker.pid
I'm not sure if is a correct approach to write at branch node, but makes sense for my use case:
I have an local instance that is my master and a web instance that is the queue consumer, which should be able to write rows that don't need to be replicated to anyone. All conflicts are already treated on application logic layer.
I have the replication configured and working, but when I write at branch node i get the following message:
Seems an expected behavior, however I didn't expect that branch node would try to insert something into queue.
Shouldn't this be optional for a branch or leaf node?
master.ini
slave.ini
ticker.ini