X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id AEF6DD1D104 for ; Wed, 31 Mar 2004 15:40:22 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 56723-06 for ; Wed, 31 Mar 2004 11:40:24 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 5218AD1C50B for ; Wed, 31 Mar 2004 11:40:20 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i2VFeLaX005091; Wed, 31 Mar 2004 10:40:21 -0500 (EST) To: "Jaime Casanova" Cc: pgsql-performance@postgresql.org Subject: Re: select slow? In-reply-to: References: Comments: In-reply-to "Jaime Casanova" message dated "Wed, 31 Mar 2004 14:27:50 +0000" Date: Wed, 31 Mar 2004 10:40:21 -0500 Message-ID: <5090.1080747621@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/441 X-Sequence-Number: 6297 "Jaime Casanova" writes: > There are no indexes yet, and the table is just 6 rows long so even if > indexes exists the planner will do a seq scan. that's my whole point 63m for > seq scan in 6 rows table is too much. That was 63 milliseconds, according to your original post, which seems perfectly reasonable to me seeing that it's not a super-duper server. The problem sounds to be either on the client side or somewhere in your network. I don't know anything about VB, but you might want to look through the client-side operations to see what could be eating up the 13 seconds. regards, tom lane