Hi Tatsuo, Can you please let us know what might be going wrong here or if you need any further information?
Regards, Nimesh. On Wed, Aug 26, 2009 at 10:07 AM, Nimesh Satam <[email protected]>wrote: > Tatsuo, > > >> What error do you have with temp table creation? > > When we try to create temp table using pgpool, the application fails with > below error: > > *"ERROR: kind mismatch among backends. Possible last query was: "..." kind > details are: 0[1] 1[E]" error.* > > We are using pgpool in master-slave mode and loadbalance=on. > > On execution of the below queries the above error appears: > > *1) CREATE TEMP TABLE tmp_ch (key integer PRIMARY KEY); * > > *2) INSERT INTO tmp_ch (key) SELECT key FROM rpt_ch WHERE id IN (135848, > 135841);* > > Note: in logs we see the first query getting Parsed on master and slave > database. But the execute is done only on slave. As a result the 2 query > fails. > > Let me know if you need any information > > Regards, > Nimesh. > > > > On Wed, Aug 26, 2009 at 5:52 AM, Tatsuo Ishii <[email protected]> wrote: > >> > Is there any significant difference in using pg connection string >> > "protocolVersion=2"? >> > >> > By default pg driver uses protocol V3, this causes the temp table >> creation >> > from application to fail. >> >> What error do you have with temp table creation? >> >> > If we change the connection string to >> > "protocolVersion=2" everything works fine >> > >> > eg: Connection c = >> > >> DriverManager.getConnection("jdbc:postgresql://db_host:db_port/reporting?protocolVersion=2","car", >> > ""); >> > >> > Is there any negative impact of using protocolversion 2. >> >> Yes. Protocolversion 2 is inefficient comparing with 3. Also you will >> lose some important features those are available with only 3. For >> example, load balance, insert lock etc. >> -- >> Tatsuo Ishii >> SRA OSS, Inc. Japan >> > >
_______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
