piled on Sep 20
2011 11:09:08"
John Udick | Enterprise Data Warehouse Development
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Wednesday, January 11, 2012 8:21 AM
To: John Udick
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #6391: insert does
"Kevin Grittner" writes:
> John Udick 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. I
John Udick 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
john.ud...@zionsbancorp.com writes:
> I would expect that at the time/date of the of now() and clock_timestamp()
> to be equal; which they are.
Well, they are not in general, but that doesn't appear to be your
problem. You have not shown us a reproducible test case, but I wonder
whether your tabl
wrote:
> PostgreSQL version: 8.4.1
You are missing years of bug fixes. You should be staying more
up-to-date on minor releases.
http://www.postgresql.org/support/versioning/
To review what has been fixed between 8.4.1 and 8.4.10, please look
through the links from 8.4.2 and up on this pag
The following bug has been logged on the website:
Bug reference: 6391
Logged by: John
Email address: john.ud...@zionsbancorp.com
PostgreSQL version: 8.4.1
Operating system: CentOS
Description:
I would expect that at the time/date of the of now() and clock_timestamp()
