X-Original-To: pgsql-odbc-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.225.181]) by svr1.postgresql.org (Postfix) with ESMTP id 8E1ACCCA80 for ; Thu, 17 Jul 2003 16:14:22 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr5.postgresql.org [64.117.225.181]) (amavisd-new, port 10024) with ESMTP id 44262-09 for ; Thu, 17 Jul 2003 16:14:40 +0000 (GMT) Received: from albert.auore.net (197.Red-80-24-20.pooles.rima-tde.net [80.24.20.197]) by svr1.postgresql.org (Postfix) with SMTP id 9B6E4CCA6A for ; Thu, 17 Jul 2003 13:14:08 -0300 (ADT) Received: (qmail 3427 invoked by uid 1000); 17 Jul 2003 16:14:35 -0000 From: Albert Cervera Areny Reply-To: albertca@jazzfree.com To: Tom Lane Subject: Re: [PERFORM] Bad performance using ODBC Date: Thu, 17 Jul 2003 18:14:16 +0200 User-Agent: KMail/1.5.9 Cc: pgsql-odbc@postgresql.org, pgsql-performance@postgresql.org References: <200307161615.13989.albertca@jazzfree.com> <18118.1058366296@sss.pgh.pa.us> In-Reply-To: <18118.1058366296@sss.pgh.pa.us> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Message-Id: <200307171814.35145.albertca@jazzfree.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/39 X-Sequence-Number: 3100 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A Dimecres 16 Juliol 2003 16:38, Tom Lane va escriure: > Albert Cervera Areny writes: > > I have a performance problem using postgresql when the connection is > > made via ODBC with a windows machine using the latests ODBC drivers > > (Windows) and PostgreSQL 7.3.3 (Linux). > > Do you have logging turned on in the ODBC driver? I recall hearing that > that adds a heck of a lot of overhead... After trying too many things I've finally been able to make it run in just = 1=20 or 2 seconds. I simply had to change the recordset type and set it to=20 dbOpenSnapshot (This one doesn't show changes made to the database once it'= s=20 been open) instead of the default dbDynaset (much more powerful but=20 unnecessary in this application). Take note that though it might seem obvious the performance loss against=20 Access isn't that much and thus VB users aren't probably used to change the= =20 recordset type. I think It would be nice a note with this performance=20 benchmarks (2 seconds against 15) in the Mini-Howto on Accessing PostgreSQL= =20 from Visual Basic. I'll contact Dave Page directly in case he finds it=20 interesting. I haven't seen any speed improvements desabling logging but thanks for your= =20 suggestion anyway! > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/FstfTK7ZP4pDOHcRArepAJ9rIhOKtztuPORbGkrVTOfC4UmUOQCeJ00u UxJegkvrs4TL3QVXNun3iFs=3D =3DitG7 -----END PGP SIGNATURE-----