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 f2FH2dx31356 for ; Thu, 15 Mar 2001 12:02:39 -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 f2FH2ct14174; Thu, 15 Mar 2001 12:02:38 -0500 (EST) To: josh@agliodbs.com cc: sqllist Subject: Re: List Concatination In-reply-to: <3AB0EDFE.998C387C@agliodbs.com> References: <3AA86767.698DDFFF@agliodbs.com> <3AA8BB73.5647B248@archonet.com> <3AB0EDFE.998C387C@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Thu, 15 Mar 2001 08:29:50 -0800" Date: Thu, 15 Mar 2001 12:02:37 -0500 Message-ID: <14171.984675757@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/314 X-Sequence-Number: 1978 Josh Berkus writes: >> Note that this is probably not a good idea - the ordering of the >> contacts will not be well-defined. When I asked about this Tom Lane was >> quite surprised that it worked, so no guarantees about long-term >> suitability. > Hmmm ... this feature is very, very, useful now that I know how to use > it. I'd love to see it hang around for future versions of PgSQL. Tom? As I said before, user-defined aggregates are certainly not going away. I don't recall the conversation Richard was thinking of, so I'm not sure exactly what was at issue there. Most likely it was some fine point, not the basic existence of the feature. regards, tom lane