Received: from mail.postgresql.org (webmail.postgresql.org [216.126.85.28]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id f2GIj3x39087 for ; Fri, 16 Mar 2001 13:45:03 -0500 (EST) (envelope-from pgsql-sql-owner@postgresql.org) Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2GGi0x23127 for ; Fri, 16 Mar 2001 11:44:00 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f2GGhjt25045; Fri, 16 Mar 2001 11:43:45 -0500 (EST) To: "Josh Berkus" cc: dev@archonet.com, sqllist Subject: Re: List Concatination In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Fri, 16 Mar 2001 08:40:22 -0800" Date: Fri, 16 Mar 2001 11:43:45 -0500 Message-ID: <25042.984761025@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/335 X-Sequence-Number: 1999 "Josh Berkus" writes: > As I said in my previous e-mail, I appear to have gotten the list to > order itself by basing it on an (ordered) sub-select. Since the DB is > only 50% populated right now, I'm not sure that's working perfectly but > I'll keep you posted. Yes, that oughta work fine to determine the order of inputs to the aggregate function. ORDER BY in sub-selects is a new feature (heck, sub-selects in FROM at all is a new feature) in 7.1, so this trick wasn't available when Richard and I discussed the issue before. regards, tom lane