X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 7BBEA329E8A for ; Sat, 2 Oct 2004 22:43:04 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 83902-01 for ; Sat, 2 Oct 2004 21:42:58 +0000 (GMT) Received: from megazone.bigpanda.com (megazone.bigpanda.com [64.147.171.210]) by svr1.postgresql.org (Postfix) with ESMTP id 73C82329E87 for ; Sat, 2 Oct 2004 22:43:00 +0100 (BST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id C96AB35779; Sat, 2 Oct 2004 14:42:57 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id C7B6A3576C; Sat, 2 Oct 2004 14:42:57 -0700 (PDT) Date: Sat, 2 Oct 2004 14:42:57 -0700 (PDT) From: Stephan Szabo To: Scott Marlowe Cc: Shane|SkinnyCorp , PgSQL ADMIN Subject: Re: PLEASE GOD HELP US! In-Reply-To: <1096751454.2611.33.camel@localhost.localdomain> Message-ID: <20041002143450.V11227@megazone.bigpanda.com> References: <00ab01c4a7f4$f04fffd0$3402a8c0@shanepc> <1096691616.2611.22.camel@localhost.localdomain> <20041002080923.C99145@megazone.bigpanda.com> <1096751454.2611.33.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/52 X-Sequence-Number: 15045 On Sat, 2 Oct 2004, Scott Marlowe wrote: > On Sat, 2004-10-02 at 09:14, Stephan Szabo wrote: > > On Fri, 1 Oct 2004, Scott Marlowe wrote: > > > > > On Fri, 2004-10-01 at 14:26, Shane | SkinnyCorp wrote: > > > > Okay, just so no one posts about this again... > > > > > > > > the 'ORDER BY t.status=5,lastreply' clause is meant to float the threads > > > > with a status of '5' to the top of the list... it is NOT meant to only grab > > > > threads where the status = 5. Oh and believe me, when I take this out of > > > > the query, it CERTAINLY doesn't add any more than possible 1/4 of a > > > > millesecond to the speed of the SELECT statement. > > > > > > > > > Wouldn't this work just as well? > > > > > > SELECT * FROM thread_listing AS t ORDER BY t.status > > > DESC,t.lastreply desc LIMIT 25 OFFSET 0 > > > > Probably not, because I don't think he wants the other statuses to have > > special ranking over the others, so a status=4 and status=1 row should be > > sorted by lastreply only effectively. This is the problem of combining > > separate status flags into a single field if you want to be doing these > > sorts of queries. > > > > So would a union give good performance? Just union the first 25 or less > with status=5 with the rest, using a 1 and 0 in each union to order by > first? Hopefully the indexes would then be used. You'd want to use union all I think and you may have to put limits on the unioned arms to get good behavior. I think the expression index would probably work without changing the query (at least for relatively low offsets) at the cost of having an extra index to maintain.