From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "John Udick" <John(dot)Udick(at)zionsbancorp(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #6391: insert does not insert correct value |
Date: | 2012-01-11 16:58:23 |
Message-ID: | 21768.1326301103@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> John Udick <John(dot)Udick(at)zionsbancorp(dot)com> wrote:
>> "PostgreSQL 8.2.15 (Greenplum Database 4.1.1.5 build 1) on
>> x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled
>> on Sep 20 2011 11:09:08"
> Yeah, I don't know how much the community lists can help with that
> implementation. It seems there is a bug in that version, but it
> might not be present in the community version.
The provided example works for me on PG 8.2.23:
regression=# select * from t order by 1;
id | d1 | d2
----+------------+------------
1 | 2012-01-11 | 2012-01-11
2 | 2012-01-11 | 2012-01-11
3 | 2012-01-11 | 2012-01-11
(3 rows)
and it does not remind me of any known/fixed bug in community 8.2.x.
So I'd have to say this is a Greenplum bug.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | r d | 2012-01-11 19:18:48 | Weird message when creating PK constraint named like table |
Previous Message | Kevin Grittner | 2012-01-11 16:37:02 | Re: BUG #6391: insert does not insert correct value |