Hi, If prepared query was used in your benchmark tool, SELECT query might be replicated. And if the SELECT query was used during transaction (BEGIN - END), it also might be replicated.
You can see what kind of queries are sent from the benchmark tool when you start replication server with debug option (-vn). Regards, --------------- At.Mitani -- original message -- From: "K, Niranjan (NSN - IN/Bangalore)"<[EMAIL PROTECTED]> To: <[email protected]> Sent: Wed, 11 Jun 2008 13:29:16 +0530 Subject: [Pgcluster-general] Read operations in PgCluster 1.9 >Hello, > >I was evaluating the pgcluster-1.9.0rc5 and the configurations are 2 >node cluster with 1 Cluster DB in each server (Master in 1 node & Slave >in another node) and 1 replicator in master node. >When i execute a tool (DB Benchmark), which executes SELECT SQL >statements, the PgCluster expects 'PgReplicate' process to be up & >running. I guess this is required only for INSERT, UPDATE, DELETE >statements. I had brought down the replicator process intensionally >because the performance (atleast for SELECT statements) was not what we >expected. Currently we get 115 transactions/ second in PgCluster and in >case of single node PotsgreSQL we get 2180 transactions/second. >What could be the potential problem. Why there is a need for SELECT >query to be submitted to Replicator process? > >I have increased the shared_buffers from 32MB to 128 MB, so that the >read rows have sufficient space in the cache. I also tried executing the >DB Benchmark tool with single thread and with 10 threads. But could not >see any major improvement. > >I'am using ODBC driver "psqlodbc-08.03.0200". > >regards, >Niranjan > > > >_______________________________________________ >Pgcluster-general mailing list >[email protected] >http://pgfoundry.org/mailman/listinfo/pgcluster-general > _______________________________________________ Pgcluster-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgcluster-general
