Le 05/23/2011 10:40 AM, Guillaume Lelarge a écrit : > Hi, > > I tried something quite simple today. I configured pgpool to have access > to one backend: > > backend_hostname0 = 'localhost' > backend_port0 = 5432 > > I configured pcp.conf, so that I could get info on my node. > > I launched PostgreSQL (9.0), and pgPool (3.0). And here is what I did > right after: > > bin/pcp_node_info 10 localhost 9898 postgres postgres 0 > localhost 5432 1 nan => this is fine > > psql -h localhost -p 9999 postgres => connection OK > > bin/pcp_node_info 10 localhost 9898 postgres postgres 0 > localhost 5432 2 nan => this is fine > > Now I detach node 0: > > bin/pcp_detach_node 10 localhost 9898 postgres postgres 0 > > bin/pcp_node_info 10 localhost 9898 postgres postgres 0 > localhost 5432 3 nan => still fine > > And then I reattach node 0: > bin/pcp_attach_node 10 localhost 9898 postgres postgres 0 > > bin/pcp_node_info 10 localhost 9898 postgres postgres 0 > localhost 5432 3 nan > > pgPool is only on connection pooling mode (no replication mode, no load > balancing mode). I was expecting to see a status 1. Is there any reason > I don't see that would explain that behaviour? >
No reason at all? so, should we fix that bug? -- Guillaume http://www.postgresql.fr http://dalibo.com _______________________________________________ Pgpool-hackers mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-hackers
