Received: from s20.highertech.net (root@s20.highertech.net [209.54.120.20]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA75662 for ; Wed, 30 Jun 1999 14:10:50 -0400 (EDT) (envelope-from jt-kirkpatrick@mpsllc.com) Received: from kirkpatrickjt (whiteoak-34.highertech.net [209.140.56.34] (may be forged)) by s20.highertech.net (8.8.6/8.8.6) with SMTP id OAA19111 for ; Wed, 30 Jun 1999 14:10:10 -0400 Received: by localhost with Microsoft MAPI; Wed, 30 Jun 1999 14:11:33 -0400 Message-ID: <01BEC302.75459D40.jt-kirkpatrick@mpsllc.com> From: JT Kirkpatrick To: "'pgsql-interfaces@hub.org'" Subject: fetching way too much or too often??? Date: Wed, 30 Jun 1999 14:11:30 -0400 Organization: MPS, LLC X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 Encoding: 13 TEXT we have about 20 folks linked to a postgres 6.4.2 database through msaccess97 and the latest odbc driver. we have declare/fetch turned on. we are having a problem with the database locking up often! i am trying to eliminate the possibilities / theories, and i am on the declare/fetch process now. when a user selects one record, as a watch on the debug window (started postmaster w/ debug 3), it is processing many (25-50? who can count that fast??) fetch 100's -- but they only selected one record from one table! why so many fetch 100's?? should i turn off declare / fetch on everyone's odbc?? thanks! jt