Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 1BA052E2D5D for ; Sat, 17 Nov 2007 17:09:40 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 86551-06 for ; Sat, 17 Nov 2007 17:09:34 -0400 (AST) Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 0830F2E2D3B for ; Sat, 17 Nov 2007 17:09:36 -0400 (AST) Received: from [192.168.1.4] (or-69-34-217-90.sta.embarqhsd.net [69.34.217.90]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id lAHLPZgn011205 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Nov 2007 13:25:38 -0800 Message-ID: <473F5886.8040702@commandprompt.com> Date: Sat, 17 Nov 2007 13:09:26 -0800 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Thunderbird 1.5.0.13 (Windows/20070809) MIME-Version: 1.0 To: Bruce Momjian CC: Tom Lane , josh@agliodbs.com, pgsql-docs@postgresql.org Subject: Re: [pgsql-advocacy] Avoiding upgrade backlash References: <200711172105.lAHL5oV02191@momjian.us> In-Reply-To: <200711172105.lAHL5oV02191@momjian.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Sat, 17 Nov 2007 13:25:38 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/70 X-Sequence-Number: 4603 Bruce Momjian wrote: > Joshua D. Drake wrote: >> Tom Lane wrote: >>> "Joshua D. Drake" writes: >>>> Honestly, I think you are underestimating this problem. >>> I fail to see why this is a major problem; and merely asserting that >>> it is one isn't going to change my mind. Can you point to something >>> like a major application that will be broken and can't easily be fixed? >> SQL-Ledger/LedgerSMB >> >> What I find interesting is that I (and Josh) are getting push back and >> all we are trying to do is be a little louder about the change. > > Adding extra warnings/notices is not a zero-cost action so there has to > be justification to do it. Actually it is near-zero cost to use but not > zero-cost to our users who have to read it multiple places. (Think dumb > product warning labels.) > > What I have done is to move the item up to the top of our > incompatibilities list in the release notes. That is near zero cost for > everyone. > Thank you. Joshua D. Drake