Re: [GENERAL] Extension to rewrite queries before execution

2015-08-16 Thread Kyotaro HORIGUCHI
Hi, although I don't see what exactly you want to do, > I am looking for an extension or a technique that will allow me to > intercept a query by the exact query text, and replace that query with a > different one. > > The context is running a third-party app which issues queries I have no > cont

Re: [GENERAL] repmgr won't update witness after failover

2015-08-16 Thread Jony Cohen
Hi, The clone command just clones the data from node2 to node1, you need to also register it with the `force` option to override the old record. (as if you're building a new replica node...) see: https://github.com/2ndQuadrant/repmgr#converting-a-failed-master-to-a-standby Regards, - Jony On Su

Re: [GENERAL] [BDR] vs pgpool-II v3

2015-08-16 Thread Craig Ringer
On 13 August 2015 at 23:52, Wayne E. Seguin wrote: > The context of this is using BDR to implement a HA solution where we have > one node getting all connections at a time, if the node fails we move all > connections to another node. (eg. only one node gets all connections at any > given time).

Re: [GENERAL] Postgresql jsonb

2015-08-16 Thread Deepak Balasubramanyam
Thank you Bill and David. I'll take a look at `pg_buffercache ` and explain with buffers. --- >>> What problem are you seeing? --- I don't have a problem at the moment. --- >>> What is your performance requirement, and what is the observed performance? ---

Re: [GENERAL] repmgr won't update witness after failover

2015-08-16 Thread Aviel Buskila
Hey, I think I know what the problem is, after the first failover when I clone the old master to be standby with the 'repmgr standby clone' command it seems that nothing updates the repl_nodes table with the new standby in my cluster so on the next failover the repmgrd is failed to find a new upcom

Re: [GENERAL] repmgr won't update witness after failover

2015-08-16 Thread Aviel Buskila
hey, I have tried to set the configuration all over again, now the status of 'repl_nodes' before the failover is: id | type | upstream_node_id | cluster | name | conninfo | priority | active +-+---++--+---