X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 9F772B430D1 for ; Wed, 9 Jul 2003 04:23:54 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 93913-03 for ; Wed, 9 Jul 2003 01:23:43 -0300 (ADT) Received: from ethereal-realms.org (thebe.ethereal-realms.org [142.179.222.205]) by svr1.postgresql.org (Postfix) with ESMTP id AC8D5B43924 for ; Wed, 9 Jul 2003 01:23:42 -0300 (ADT) Received: from ethereal-realms.org (ip14.ethereal-realms.COM [192.168.1.14]) by ethereal-realms.org (8.12.6/8.12.6) with ESMTP id h694NeUc024080; Tue, 8 Jul 2003 22:23:40 -0600 (MDT) Message-ID: <3F0B98CA.90800@ethereal-realms.org> Date: Tue, 08 Jul 2003 22:23:38 -0600 From: Martin Foster Organization: Ethereal Realms User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stephan Szabo , PostgreSQL Performance Subject: Re: Efficiency of timestamps References: <20030708192541.D5781-100000@megazone23.bigpanda.com> In-Reply-To: <20030708192541.D5781-100000@megazone23.bigpanda.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/150 X-Sequence-Number: 2443 Stephan Szabo wrote: > > > The row estimate is high. How many rows meet the various conditions and > some of the combinations? And how many rows does it estimate if you do a > simpler query on those with explain? > > I still think some variety of multi-column index to make the above index > conditions would help, but you'd probably need to play with which ones > help, and with the cost cut for the limit, I don't know if it'd actually > get a better plan, but it may be worth trying a bunch and seeing which > ones are useful and then dropping the rest. > > At any given point in time you would not expect to see much more then 30 posts applying for a time based search. That is primarily a result of having more then one room for which posts are attached to, and then some posts exist just to show people are there et cetera. Simpler queries seem to do quiet well. That view makes use of the same table and seems to have no performance impact from doing as such, and the position based search is considerably faster. I can show EXPLAIN ANALYSE for all of those if you wish. Martin Foster Creator/Designer Ethereal Realms martin@ethereal-realms.org