Tomasz Chmielewski wrote: > - backend0 has weight 1; backend1 has weight 0 - doesn't in mean these > queries should be sent to backend0? Right now, backend0 gets only few > queries; backend1 gets thousands.
I guess I didn't reload postgres settings on one of the servers, so it was not logging everything it should. Sorry for confusion :| To confirm - should such a query go to a backend with weight 0? I suppose it should, since it's transaction which could result in a write? [110-1] 2010-03-01 08:51:46 SGT LOG: duration: 0.038 ms statement: BEGIN [111-1] 2010-03-01 08:51:46 SGT LOG: duration: 0.032 ms statement: SET DATESTYLE TO 'ISO' [112-1] 2010-03-01 08:51:46 SGT LOG: duration: 0.036 ms statement: COMMIT [113-1] 2010-03-01 08:51:46 SGT LOG: duration: 0.059 ms statement: SHOW client_encoding [114-1] 2010-03-01 08:51:46 SGT LOG: duration: 0.053 ms statement: SHOW default_transaction_isolation [115-1] 2010-03-01 08:51:46 SGT LOG: duration: 0.043 ms statement: BEGIN; SET TRANSACTION ISOLATION LEVEL READ COMMITTED [116-1] 2010-03-01 08:51:46 SGT LOG: duration: 0.034 ms statement: SET TIME ZONE E'Asia/Singapore' [117-1] 2010-03-01 08:51:46 SGT LOG: duration: 0.037 ms statement: ROLLBACK [118-1] 2010-03-01 08:51:46 SGT LOG: duration: 0.054 ms statement: DISCARD ALL -- Tomasz Chmielewski http://wpkg.org _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
