Hi, We are using pgpool 2.2.2 in 'Master/Slave mode' and Loadbalance mode.
With postgres version: 8.3.3 (jdbc driver postgresql-8.3-603.jdbc3.jar and postgresql-8.1-407.jdbc3.jar for 2 different applications). Slony is used for database replication. How does temporary table creation work? The application fails when it creates a temp table as the SELECT request is going on slave database instead of master. As per understanding the temp table gets created on master and all the queries are sent to the master server itself. But thats not happening in the current way. All the 4 queries are in a single transaction. Can someone highlight if this is a bug in pgpool? The queries are executed in the following order: 1) CREATE TEMP TABLE tmp_met AS SELECT * from x.x; 2) CREATE INDEX tmp_met_indx ON tmp_met(id); 3) CREATE TEMP TABLE tmp_ch (key integer PRIMARY KEY); *4) INSERT INTO tmp_ch (key) SELECT key FROM rpt_ch WHERE id IN (135848, 135841);* Regards, Nimesh
_______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
