Hi Fernando, Thanks for the info. Oh, pgpool's recovery process connects to template1. That was the cause of the problem. Pgpool should connects to "postgres" database instead of template1, I think. Will fix. -- Tatsuo Ishii SRA OSS, Inc. Japan
> Hi Tatsuo, > > Thanks for your answer. Looking at the logs i found that the error was: > > ERROR: source database "template1" is being accessed by other users > DETAIL: There are 1 other session(s) using the database. > STATEMENT: create database test123; > > So i just have to take care for not running CREATE TABLE when a node > is being recovered. > > Regards, > --- > > Fernando Marcelo > www.consultorpc.com > ferna...@consultorpc.com > Tel: +34 902 998971 > Fax: +34 91 7903701 > > ## legal disclaimer > > The information contained in this email is confidential. It is > intended only > for the stated addressee(s) and access to it by any other person is > unauthorized. If you are not an addressee, you must not disclose, copy, > circulate or in any other way use or rely on the information contained > in > this email. Such unauthorized use may be unlawful. If you have > received this > email in error, please inform us immediately by emailing ad...@consultorpc.com > and delete it and all copies from your system. > > ## end mail > > Em 22/12/2009, às 01:57, Tatsuo Ishii escreveu: > > >> Hello, > >> > >> I have pgpool setup with 4 postgres nodes. I tried to run the > >> following test with: > >> > >> 3 Active nodes > >> 1 Failed nodes > >> > >> While recovering the failed node i decided to connect on pgpool and > >> run a simple create database. What i got was: > >> > >> # create database test123; > >> ERROR: kind mismatch among backends. Possible last query was: > >> "create > >> database test123;" kind details are: 0[E] 1[C] 3[C] > > > > You should find something in the PostgreSQL log of node 0. > > (0[E] means node 0 PostgreSQL reported error condition, while 1[C] > > means the operation completed noramly). > > > > Note that pgpool-II 2.3.1 reports PostgreSQL error in case [E], which > > should make admin's life a little bit easier. > > -- > > Tatsuo Ishii > > SRA OSS, Inc. Japan > > > >> HINT: check data consistency among db nodes > >> server closed the connection unexpectedly > >> This probably means the server terminated abnormally > >> before or while processing the request. > >> The connection to the server was lost. Attempting reset: Succeeded. > >> > >> An this caused one of the nodes to be at an inconsistency state > >> ( without test123 database ). > >> > >> Do you know what could have caused this problem? Do i have to stop > >> pgpool when running pcp_recovery_node? > >> > >> Thanks, > >> --- > >> > >> Fernando Marcelo > >> www.consultorpc.com > >> ferna...@consultorpc.com > >> Tel: +34 902 998971 > >> Fax: +34 91 7903701 > >> > >> ## legal disclaimer > >> > >> The information contained in this email is confidential. It is > >> intended only > >> for the stated addressee(s) and access to it by any other person is > >> unauthorized. If you are not an addressee, you must not disclose, > >> copy, > >> circulate or in any other way use or rely on the information > >> contained > >> in > >> this email. Such unauthorized use may be unlawful. If you have > >> received this > >> email in error, please inform us immediately by emailing > >> ad...@consultorpc.com > >> and delete it and all copies from your system. > >> > >> ## end mail > >> > >> _______________________________________________ > >> Pgpool-general mailing list > >> Pgpool-general@pgfoundry.org > >> http://pgfoundry.org/mailman/listinfo/pgpool-general > > _______________________________________________ > Pgpool-general mailing list > Pgpool-general@pgfoundry.org > http://pgfoundry.org/mailman/listinfo/pgpool-general _______________________________________________ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
