[Pgpool-hackers] patch to add node_id column in pool_nodes "view"

Tatsuo Ishii ishii at sraoss.co.jp
Thu Nov 18 01:58:58 UTC 2010


> Next step is to add a new column about Read/Write or Read Only status of
> the node.
> 
> In Master/Slave mode it could be usefull to know who's the "master" (in
> case of a failback(.sh) it will be old_node+1 so, at the first failover
> it will be 0+1=1, the next will be 1+1=2, etc..

In CVS HEAD failover script can know who *was* the primary(%P).

> I *know* pgpool-II does only *assume* (am I right?) who's the master,
> but doesn't *yet* know for sure the master is in R/W ... because its all
> about the good execution of failback.sh (exit 0). If failback.sh
> succeeds, then pgpool-II *assumes* the n+1 is the new master...

In CVS HEAD after failover pgpool-II tries to make sure that which one
is the primary by using find_primary_node().

> So for the moment the column "Read-Write status" will only be based on
> what pgpool-II *assumes* to be... I think next step then is to be sure
> that the master is in R/W :)

It's already done.

> This completes the reflexion on the thread on pgpool-general whose
> subject is " Suggestion for Failover on Master/Slave Streaming
> Replication"...
> 
> Now, digging back into pgpool-II code ;)
> 
> Cheers,
> 
> -- 
> Jean-Paul Argudo
> www.PostgreSQL.fr
> www.Dalibo.com
> _______________________________________________
> Pgpool-hackers mailing list
> Pgpool-hackers at pgfoundry.org
> http://pgfoundry.org/mailman/listinfo/pgpool-hackers


More information about the Pgpool-hackers mailing list