Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id CB7A52E15CD for ; Tue, 13 Nov 2007 20:11:07 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 96484-10 for ; Tue, 13 Nov 2007 20:11:06 -0400 (AST) Received: from mail.planetcobalt.net (mail.planetcobalt.net [217.10.9.49]) by postgresql.org (Postfix) with ESMTP id 440772E17F6 for ; Tue, 13 Nov 2007 20:11:05 -0400 (AST) Received: by mail.planetcobalt.net (Postfix, from userid 1000) id B31BE3C00084; Wed, 14 Nov 2007 01:11:03 +0100 (CET) Date: Wed, 14 Nov 2007 01:11:03 +0100 From: Ansgar -59cobalt- Wiechers To: pgsql-performance@postgresql.org Subject: Re: Curious about dead rows. Message-ID: <20071114001103.GA20319@mail.planetcobalt.net> References: <20071112190833.GY32349@crankycanuck.ca> <4739BD65.9070605@verizon.net> <20071113152111.GG11563@crankycanuck.ca> <473A0023.5020609@verizon.net> <20071113213510.GF11563@crankycanuck.ca> <473A1DC3.3070608@verizon.net> <20071113221028.GH11563@crankycanuck.ca> <473A2EAD.9040107@verizon.net> <20071113235133.GI19014@alvh.no-ip.org> <90bce5730711131559k7786564eve2a3e9dd9596377a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <90bce5730711131559k7786564eve2a3e9dd9596377a@mail.gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/205 X-Sequence-Number: 27620 On 2007-11-13 Trevor Talbot wrote: > On 11/13/07, Alvaro Herrera wrote: >> Jean-David Beyer wrote: >>> Sorry. Most of the lists I send to have ReplyTo set, but a few do >>> not. And then I forget. >> >> If you use "reply to all", it works wonderfully in both cases. > > Then it upsets the people who don't want to get private copies, only > list copies, on most of the Reply-To lists. > > There's no winning :( Unless you use a mailer that supports Reply, Group-Reply, *and* List-Reply. ;) Regards Ansgar Wiechers -- "The Mac OS X kernel should never panic because, when it does, it seriously inconveniences the user." --http://developer.apple.com/technotes/tn2004/tn2118.html