X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 83D89D1B53A for ; Thu, 20 Nov 2003 15:38:45 +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 45648-10 for ; Thu, 20 Nov 2003 11:38:18 -0400 (AST) Received: from fzkmail2.fzk.de (fzkmail2.fzk.de [141.52.27.52]) by svr1.postgresql.org (Postfix) with SMTP id B3E76D1B50A for ; Thu, 20 Nov 2003 11:38:12 -0400 (AST) Received: FROM resy5.fzk.de BY fzkmail2.fzk.de ; Thu Nov 20 16:38:14 2003 +0100 Received: œby rodos.fzk.de with ESMTP (8.8.6 (PHNE_17135)/8.7.1) id QAA04255; Thu, 20 Nov 2003 16:38:14 +0100 (MET) Message-ID: <3FBCDFE5.9F3AEF69@rodos.fzk.de> Date: Thu, 20 Nov 2003 16:38:14 +0100 From: Christoph Haller X-Mailer: Mozilla 4.77 [en] (X11; U; HP-UX B.10.20 9000/780) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-sql@postgresql.org, wintrojr@tripos.com Subject: Re: Need another way to do this, my sql much to slow... Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Amavis-Alert: BAD HEADER Non-encoded 8-bit data (char 9C hex) in message header 'Received' Received: \234by rodos.fzk.de... ^ X-Archive-Number: 200311/251 X-Sequence-Number: 16066 > > I am attempting to write a spam management add-on for my corporate > server, I have the database and the apps written but one part is WAY to > slow to be usefull. > > The following view: > > Column | Type | Modifiers > -----------------------+---------+----------- > env_sender_num | integer | > msg_from_claims_count | bigint | > > is built on the follow table: > > Column | Type | Modifiers > -----------------+-----------------------------+----------- > msg_sender_num | integer | > env_sender_num | integer | > msg_from_domain | character varying(255) | > env_from_domain | character varying(255) | > recorded_date | timestamp without time zone | > Indexes: record_of_claims_env_sender_num_idx btree (env_sender_num), > record_of_claims_msg_sender_num_idx btree (msg_sender_num) > > With the following SQL: > > > SELECT record_of_claims.env_sender_num, count(DISTINCT > record_of_claims.msg_sender_num) > AS msg_from_claims_count=20 > FROM record_of_claims=20 > GROUP BY record_of_claims.env_sender_num; > > A sample dataset follows: > [snip] Not sure, if this can speed up things SELECT env_sender_num, COUNT(msg_sender_num) AS msg_from_claims_count FROM ( SELECT DISTINCT ON (msg_sender_num) msg_sender_num,env_sender_num FROM record_of_claims ORDER BY msg_sender_num,env_sender_num DESC ) foo GROUP BY env_sender_num; but possibly it inspires you or someone else for a better one. Regards, Christoph