To: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
cc: "Robert Haas" <robertmhaas@gmail.com>, pgsql-bugs@postgresql.org,
	"Jon Nelson" <jnelson+pgsql@jamponi.net>
Subject: Re: [PERFORM] typoed column name, but postgres didn't grump 
In-reply-to: <4CCADE440200002500036FB2@gw.wicourts.gov> 
References: <AANLkTimYMA8D2h4-jHK5vD032jWwig1iJmW6uF-3i=Bx@mail.gmail.com>
	<4480.1288374498@sss.pgh.pa.us>
	<4CCACE6E0200002500036F95@gw.wicourts.gov>
	<6240.1288379246@sss.pgh.pa.us>
	<AANLkTim35FrP1EyZRmnotKSw=2rq8JNVutkitn9PXwFp@mail.gmail.com>
	<4CCADE440200002500036FB2@gw.wicourts.gov>
Comments: In-reply-to "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
	message dated "Fri, 29 Oct 2010 14:46:28 -0500"
Date: Fri, 29 Oct 2010 16:12:42 -0400
Message-ID: <8216.1288383162@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Robert Haas <robertmhaas@gmail.com> wrote:
>>> I think if I had to pick a proposal, I'd say we should disable #2
>>> for the specific case of casting a composite type to something
>>> else.
 
>> Well, then let's do that.  It's not the exact fix I'd pick, but
>> it's clearly better than nothing, so I'm willing to sign on to it
>> as a compromise position.

> So, I'd rather scrap #2 entirely; but if that really would break
> much working code, +1 for ignoring it when it would cast a composite
> to something else.

Well, assuming for the sake of argument that we have consensus on fixing
it like that, is this something we should just do in HEAD, or should we
back-patch into 8.4 and 9.0?  We'll be hearing about it nigh
indefinitely if we don't, but on the other hand this isn't the kind of
thing we like to change in released branches.

			regards, tom lane