I couldn't reproduce the problem. Any hint to reproduce it? -- Tatsuo Ishii SRA OSS, Inc. Japan
> Thanks for the report. I will look into this. > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > > > Hi, > > > > I'm wondering why this is caused when I run the following as a quick > > test. > > can this syntax error cause any DB mismatch and make the DB get out of > > sync cause on a real scenario, one time a few minutes after that > > showed in the logs I saw a kind mismatch over and over until I pulled > > node 1 out. > > > > pgpool server: > > nast=# set statement_timeout TO 100; > > SET > > > > nast=# SELECT count(*) from instance group by id order by id ; > > ERROR: canceling statement due to statement timeout > > > > node 0: > > 2009-03-23 00:12:03 UTC 949 0ERROR: canceling statement due to > > statement timeout > > 2009-03-23 00:12:03 UTC 949 0STATEMENT: SELECT count(*) from instance > > group by id order by id ; > > > > node 1: > > 2009-03-23 00:12:03 UTC 9075 0ERROR: syntax error at or near "send" > > at character 1 > > 2009-03-23 00:12:03 UTC 9075 0STATEMENT: send invalid query from > > pgpool to abort transaction > > > > Thank you, > > > > Marcelo > > PostgreSQL DBA > > Linux/Solaris System Administrator > > > > > _______________________________________________ > Pgpool-general mailing list > [email protected] > http://pgfoundry.org/mailman/listinfo/pgpool-general _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
