From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "Merlin Moncure" <mmoncure(at)gmail(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Jon Nelson" <jnelson+pgsql(at)jamponi(dot)net>, <pgsql-bugs(at)postgresql(dot)org>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: [PERFORM] typoed column name, but postgres didn't grump |
Date: | 2010-11-05 20:15:38 |
Message-ID: | 4CD41F9A020000250003737F@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-performance |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Here's a proposed patch, sans documentation as yet.
I see you took the surgical approach -- only a cast from a record to
a character string type is affected. I agree that will fix the
complaints I've seen, and I imagine you're keeping the change narrow
to minimize the risk of breaking existing code, but this still looks
weird to me:
test=# select ('2010-11-05'::date).text;
text
------------
2010-11-05
(1 row)
Oh, well -- I guess you have to go well out of your way to shoot
your foot with such cases, so that's probably for the best.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-11-05 20:23:00 | Re: [PERFORM] typoed column name, but postgres didn't grump |
Previous Message | Tom Lane | 2010-11-05 19:17:24 | Re: [PERFORM] typoed column name, but postgres didn't grump |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2010-11-05 20:19:37 | Re: Major Linux performance regression; shouldn't we be worried about RHEL6? |
Previous Message | Josh Berkus | 2010-11-05 20:15:20 | Major Linux performance regression; shouldn't we be worried about RHEL6? |