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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: "Robert Haas" <robertmhaas(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org, "Jon Nelson" <jnelson+pgsql(at)jamponi(dot)net>
Subject: Re: [PERFORM] typoed column name, but postgres didn't grump
Date: 2010-10-29 20:12:42
Message-ID: 8216.1288383162@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-performance

"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Robert Haas <robertmhaas(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kevin Grittner 2010-10-29 20:21:09 Re: [PERFORM] typoed column name, but postgres didn't grump
Previous Message Robert Haas 2010-10-29 20:05:32 Re: What happened to SSL_CIPHERS?

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2010-10-29 20:21:09 Re: [PERFORM] typoed column name, but postgres didn't grump
Previous Message Kevin Grittner 2010-10-29 19:46:28 Re: [PERFORM] typoed column name, but postgres didn't grump