Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id AD62F2E2D67 for ; Sat, 17 Nov 2007 01:47:33 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 17879-01 for ; Sat, 17 Nov 2007 01:47:29 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id D26252E2D3B for ; Sat, 17 Nov 2007 01:47:30 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lAH5lSpB010224; Sat, 17 Nov 2007 00:47:28 -0500 (EST) To: josh@agliodbs.com cc: pgsql-docs@postgresql.org Subject: Re: [pgsql-advocacy] Avoiding upgrade backlash In-reply-to: <200711162107.17437.josh@agliodbs.com> References: <200711152000.lAFK08911889@momjian.us> <200711162107.17437.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Fri, 16 Nov 2007 21:07:17 -0800" Date: Sat, 17 Nov 2007 00:47:27 -0500 Message-ID: <10223.1195278447@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/61 X-Sequence-Number: 4594 Josh Berkus writes: > Hmmm. I don't feel like it contains a clear warning, though. We need a > statement like: > Some users may encounter issues upgrading due to the changes in handling > data type casts. If you suspect that your schema or application may not > be handling data type comparisons cleanly, you are strongly urged to test > for casting error messages before upgrading your production server. When have we ever suggested that people *shouldn't* test their apps before committing to a major version update? I think the whole thing has been significantly overblown. We have made incompatible changes bigger than this one --- and, often, harder to find let alone fix --- in almost every major release. This one you can at least be pretty sure that you will get an error, and not a silent change in behavior, if you fall foul of it. regards, tom lane