Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E2A9E9FA18B for ; Thu, 30 Nov 2006 12:08:42 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 45982-10 for ; Thu, 30 Nov 2006 12:08:34 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from ai.4ph.com (ai.4ph.com [66.117.56.228]) by postgresql.org (Postfix) with ESMTP id ED8449F9ECF for ; Thu, 30 Nov 2006 12:08:33 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by ai.4ph.com (Postfix) with ESMTP id EE547230805E; Thu, 30 Nov 2006 11:02:23 -0500 (EST) X-Virus-Scanned: amavisd-new at Received: from ai.4ph.com ([127.0.0.1]) by localhost (ai.4ph.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OgOccT5fL4Yd; Thu, 30 Nov 2006 11:02:21 -0500 (EST) Received: from ai.4ph.com (ai.4ph.com [66.117.56.228]) by ai.4ph.com (Postfix) with ESMTP id CDC36230801F; Thu, 30 Nov 2006 11:02:21 -0500 (EST) Message-ID: <17835952.62811164902540562.JavaMail.root@srv161.carpathiahost.net> Date: Thu, 30 Nov 2006 11:02:20 -0500 (EST) From: Jeff Herrin To: Michael Fuhr Subject: Re: consistent random order Cc: pgsql-sql@postgresql.org In-Reply-To: <20061130075822.GA85484@winnie.fuhr.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/295 X-Sequence-Number: 26947 Michael, I think you may have solved my problem. We're still experimenting with it but I think setseed is going to work. Thank you very, very much! Jeff Herrin ----- Original Message ----- From: Michael Fuhr To: Jeff Herrin Cc: Andreas Kretschmer , pgsql-sql@postgresql.org Sent: Thursday, November 30, 2006 2:58:23 AM GMT-0500 US/Eastern Subject: Re: [SQL] consistent random order On Wed, Nov 29, 2006 at 12:32:56PM -0500, Jeff Herrin wrote: > I don't think cursors are going to help in this case. The order > by random() is still going to give different result sets on different > pages. Have you tried using setseed() to seed the random number generator to the same value before each query? -- Michael Fuhr ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq