| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | PropAAS DBA <dba(at)propaas(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pentaho timestamp issue |
| Date: | 2018-03-18 23:13:03 |
| Message-ID: | 15125.1521414783@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
PropAAS DBA <dba(at)propaas(dot)com> writes:
> Pinging the list on the off chance someone has dealt with this and knows
> of a workaroud. We have pentaho pointing to a PostgreSQL v10.3 database,
> getting this error:
> 2018/03/18 15:06:37 - INPUT STEP - Fact.0 - Bad value for type
> timestamp : 0001-02-04 17:00:04-06:59:56
Hmm. Presumably, this is coming from something that thinks that 1 AD
is outside the reasonable range of timestamps. Assuming you agree that
such a value shouldn't appear in your application, I'd look for timestamps
getting put into the database using to_timestamp() with a format string
that doesn't really match the data, causing the year field to be truncated
or misinterpreted.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Johann Spies | 2018-03-19 07:30:20 | Logical replication: duplicate key problem |
| Previous Message | PropAAS DBA | 2018-03-18 21:54:04 | pentaho timestamp issue |