Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id CE15B133616B for ; Thu, 4 Nov 2010 13:56:32 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 01653-04 for ; Thu, 4 Nov 2010 16:56:25 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 541601337B5C for ; Thu, 4 Nov 2010 13:56:25 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id oA4GuKi3011058; Thu, 4 Nov 2010 12:56:20 -0400 (EDT) To: Merlin Moncure cc: Kevin Grittner , Robert Haas , Jon Nelson , pgsql-bugs@postgresql.org Subject: Re: [PERFORM] typoed column name, but postgres didn't grump In-reply-to: References: <4480.1288374498@sss.pgh.pa.us> <4CCACE6E0200002500036F95@gw.wicourts.gov> <6240.1288379246@sss.pgh.pa.us> <4CCADE440200002500036FB2@gw.wicourts.gov> <8216.1288383162@sss.pgh.pa.us> <4CD28C5C020000250003727B@gw.wicourts.gov> <9974.1288887285@sss.pgh.pa.us> Comments: In-reply-to Merlin Moncure message dated "Thu, 04 Nov 2010 12:48:08 -0400" Date: Thu, 04 Nov 2010 12:56:20 -0400 Message-ID: <11057.1288889780@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201011/37 X-Sequence-Number: 28617 Merlin Moncure writes: > On Thu, Nov 4, 2010 at 12:14 PM, Tom Lane wrote: >> "Kevin Grittner" writes: >>> Merlin Moncure wrote: >>>> create type x as (a int, b int); >>>> select f((1,2)); >> I think Merlin probably meant to write "select x((1,2))", but that >> doesn't work out-of-the-box either.  What would be affected is >> something like > Actually I didn't -- I left out that there was a function f taking x. Ah. No, that would still work after the change. The case that I'm proposing to break is using function-ish notation to invoke a cast from a composite type to some other type whose name you use as if it were a function. Even there, if you've created such a cast following the usual convention of naming the cast function after the target type, it'll still act the same. It's just the built-in I/O-based casts that will stop working this way (for lack of a matching underlying function). regards, tom lane