Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 0F0059FB474 for ; Wed, 18 Apr 2007 19:44:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 40273-08 for ; Wed, 18 Apr 2007 19:44:00 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from weatherbeeta.com.au (218-214-212-153.people.net.au [218.214.212.153]) by postgresql.org (Postfix) with SMTP id 9DC4A9FA467 for ; Wed, 18 Apr 2007 19:44:09 -0300 (ADT) Received: (qmail 13150 invoked from network); 18 Apr 2007 22:44:05 -0000 X-NetworkBox-HamSign: 0101;OUT;wbeetaau1;bceb3dbbdd74bbc37048dc365981a2c5; Received: from mail.weatherbeeta.com.au (10.10.0.2) by network-box.weatherbeeta.com.au with SMTP; 18 Apr 2007 22:44:05 -0000 Received: (qmail 31936 invoked by uid 1166); 19 Apr 2007 08:44:00 +1000 Received: from 172.20.0.155 by mail.weatherbeeta.com.au (envelope-from , uid 1165) with qmail-scanner-1.25-st-qms (clamdscan: 0.88.6/2315. perlscan: 1.25-st-qms. Clear:RC:1(172.20.0.155):. Processed in 0.222165 secs); 18 Apr 2007 22:44:00 -0000 X-Antivirus-mail.weatherbeeta.com.au-Mail-From: phillip.smith@weatherbeeta.com.au via mail.weatherbeeta.com.au X-Antivirus-mail.weatherbeeta.com.au: 1.25-st-qms (Clear:RC:1(172.20.0.155):. Processed in 0.222165 secs Process 31927) Received: from it-phil.weatherbeeta.com.au (HELO wbaus090) (172.20.0.155) by mail.weatherbeeta.com.au with SMTP; 19 Apr 2007 08:43:59 +1000 From: "Phillip Smith" To: "'Stuart McGraw'" , Subject: Re: slowness when subselect uses DISTINCT Date: Thu, 19 Apr 2007 08:43:49 +1000 Organization: Weatherbeeta Pty Ptd Message-ID: <002a01c7820b$07ee3010$9b0014ac@wbaus090> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Importance: Normal X-Scanned-By-wbeetaau1: Virus scan performed by network-box X-Scanned-By-wbeetaau1: Scanner file id is wbeetaau1-1176936245.119-13145-000 X-Scanned-By-wbeetaau1: No known viruses found in message (received+scanned in 0.02/0.08 secs) X-Scanned-By-wbeetaau1: Spam-Check-Result: No, hits=0 required=7 tests= autolearn=no version=2.0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/161 X-Sequence-Number: 28161 May I suggest you post an EXPLAIN ANALYZE to the group for the query = you're having problems with...? -----Original Message----- From: pgsql-sql-owner@postgresql.org = [mailto:pgsql-sql-owner@postgresql.org] On Behalf Of Stuart McGraw Sent: Thursday, 19 April 2007 04:17 To: pgsql-sql@postgresql.org Subject: [SQL] slowness when subselect uses DISTINCT I have several times now run into what seems like similar performance problems with some=20 of my postgresql queries. I have a view that runs reasonably quicky. I use this view in a subselect in another=20 query and that query too runs reasonably quicky. The view returns some unwanted duplicate=20 rows so I modify it using either DISTINCT=20 or GROUP BY to eliminate them. View still runs reasonably quickly. I use the modified view as a subselect as above, but now the query runs 2-3 orders of magnitude more slowly than before. Before I go through the effort of putting=20 together a specific and concise test case,=20 has anyone seen this general pattern and=20 have an explanation or advice? (PG-8.2.3) ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate *******************Confidentiality and Privilege Notice******************* The material contained in this message is privileged and confidential to the addressee. If you are not the addressee indicated in this message or responsible for delivery of the message to such person, you may not copy or deliver this message to anyone, and you should destroy it and kindly notify the sender by reply email. Information in this message that does not relate to the official business of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta. Weatherbeeta, its employees, contractors or associates shall not be liable for direct, indirect or consequential loss arising from transmission of this message or any attachments