Re: BUG #6391: insert does not insert correct value - Mailing list pgsql-bugs

From Kevin Grittner
Subject Re: BUG #6391: insert does not insert correct value
Date
Msg-id 4F0D664E02000025000446AA@gw.wicourts.gov
Whole thread Raw
In response to BUG #6391: insert does not insert correct value  (john.udick@zionsbancorp.com)
Responses Re: BUG #6391: insert does not insert correct value  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
John Udick <John.Udick@zionsbancorp.com> wrote:

> We did notice that although now() failed, changing this to
> 'now()'::date works (using single quotes around now()).

That seem unrelated to the now() function.  Casting a literal to a
date/time/timestamp supports parsing out certain keywords, like
'now', 'today', 'yesterday', and 'tomorrow'.  It's probably ignoring
those parentheses.

> Also, apparently we are not truly a Postgres database, but EMC's
> Greenplum database. I will be working with our admins and EMC,
> unless someone in Postgres can point out a specific version that
> resolved this issue.

> "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.

-Kevin

pgsql-bugs by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Postgres Backup and Restore
Next
From: Tom Lane
Date:
Subject: Re: BUG #6391: insert does not insert correct value