Received: from p1.selectacast.net (p1.selectacast.net [206.41.1.251]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2JNsPN16386 for ; Mon, 19 Mar 2001 18:54:25 -0500 (EST) (envelope-from jks@selectacast.net) Received: from selectacast.net (IDENT:jks@d1 [209.219.91.66]) by p1.selectacast.net (8.9.3/8.9.3) with ESMTP id SAA10173; Mon, 19 Mar 2001 18:54:06 -0500 Message-ID: <3AB69C1E.2EE4841D@selectacast.net> Date: Mon, 19 Mar 2001 18:54:06 -0500 From: Joseph Shraibman Organization: Xtenit, Inc. http://www.xtenit.com X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2 i686) X-Accept-Language: en MIME-Version: 1.0 To: David Olbersen CC: "Fernando Eduardo B. L. e Carvalho" , Postgresql Subject: Re: Select very slow... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200103/380 X-Sequence-Number: 2046 David Olbersen wrote: > > On Sun, 18 Mar 2001, Fernando Eduardo B. L. e Carvalho wrote: > > > select p.city,count(*) from sales s, person p where s.doc = p.doc > > group by p.city; > > > > Anyone help-me? > > 1: VACUUM ANALYZE sales > VACUUM ANALYZE person; > > 2: That 'count(*)' is going to be slow. > Try counting a column that's indexed (p.doc might work?) > I don't think that is true. -- Joseph Shraibman jks@selectacast.net Increase signal to noise ratio. http://www.targabot.com