Re: [PERFORM] typoed column name, but postgres didn't grump

"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>> Trying to understand real world cases that this would
>> break...would the following now fail w/o explicit cast?
>>
>> create type x as (a int, b int);
>> select f((1,2));

> It already does:

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

select text((1,2));

which you'd now be forced to write as

select (1,2)::text;

(or you could use CAST notation; but not text(row) or row.text).

regards, tom lane