Re: Joel's Performance Issues WAS : Opteron vs Xeon - Mailing list pgsql-performance

From Joel Fradkin
Subject Re: Joel's Performance Issues WAS : Opteron vs Xeon
Date
Msg-id 005c01c54681$eecaf0d0$797ba8c0@jfradkin
Whole thread Raw
In response to Re: Joel's Performance Issues WAS : Opteron vs Xeon  ("Mohan, Ross" <RMohan@arbinet.com>)
List pgsql-performance
Here is the connect string I am using.
It could be horrid as I cut it from ODBC program.

Session("StringConn") =
"DRIVER={PostgreSQL};DATABASE=wazagua;SERVER=192.168.123.252;PORT=5432;UID=;
PWD=;ReadOnly=0;Protocol=6.4;FakeOidIndex=0;ShowOidColumn=0;RowVersioning=0;
ShowSystemTables=0;ConnSettings=;Fetch=100;Socket=4096;UnknownSizes=0;MaxVar
charSize=254;MaxLongVarcharSize=8190;Debug=0;CommLog=0;Optimizer=1;Ksqo=1;Us
eDeclareFetch=0;TextAsLongVarchar=1;UnknownsAsLongVarchar=0;BoolsAsChar=1;Pa
rse=0;CancelAsFreeStmt=0;ExtraSysTablePrefixes=dd_;LFConversion=1;UpdatableC
ursors=1;DisallowPremature=0;TrueIsMinus1=0;BI=0;ByteaAsLongVarBinary=0;UseS
erverSidePrepare=0"

Joel Fradkin


-----Original Message-----
From: Mohan, Ross [mailto:RMohan@arbinet.com]
Sent: Thursday, April 21, 2005 9:42 AM
To: jfradkin@wazagua.com
Subject: RE: [PERFORM] Joel's Performance Issues WAS : Opteron vs Xeon

FWIW, ODBC has variables to tweak, as well. fetch/buffer sizes, and the
like.

Maybe one of the ODBC cognoscenti here can chime in more concretely....






pgsql-performance by date:

Previous
From: "Shoaib Burq (VPAC)"
Date:
Subject: Re: two queries and dual cpu (perplexed)
Next
From: "Shoaib Burq (VPAC)"
Date:
Subject: Re: two queries and dual cpu (perplexed)