Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id E7122476141; Sun, 6 Oct 2002 23:20:40 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 3D9E8476086; Sun, 6 Oct 2002 23:20:40 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g973KYhR015764; Sun, 6 Oct 2002 23:20:34 -0400 (EDT) To: Curt Sampson Cc: pgsql-general , pgsql-hackers@postgresql.org Subject: cross-posts (was Re: Large databases, performance) In-reply-to: References: Comments: In-reply-to Curt Sampson message dated "Mon, 07 Oct 2002 11:27:04 +0900" Date: Sun, 06 Oct 2002 23:20:33 -0400 Message-ID: <15763.1033960833@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/330 X-Sequence-Number: 31328 Curt Sampson writes: > ... Avoiding cross-posting would be nice, since I am getting lots of > duplicate messages these days. Cross-posting is a fact of life, and in fact encouraged, on the pg lists. I suggest adapting. Try sending set all unique your-email-address to the PG majordomo server; this sets you up to get only one copy of each cross-posted message. regards, tom lane