Re: Date Format 9999-12-31-00.00.00.000000

2020-10-16 Thread Laurenz Albe
On Thu, 2020-10-15 at 20:58 +, Dirk Krautschick wrote: > because of a migration from DB2 we have a lot of timestamps like > > -12-31-00.00.00.00 > > What would be the best way to handle this in Postgres also related > to overhead and performance (index usage?). > > Or is > > TO_TIM

Re: Date Format 9999-12-31-00.00.00.000000

2020-10-15 Thread Kyotaro Horiguchi
At Thu, 15 Oct 2020 17:59:39 -0700, Adrian Klaver wrote in > On 10/15/20 1:58 PM, Dirk Krautschick wrote: > > Hi, > > because of a migration from DB2 we have a lot of timestamps like > > -12-31-00.00.00.00 > > I'm assuming these got stored in a varchar field? It seems like an (old-styl

Re: Date Format 9999-12-31-00.00.00.000000

2020-10-15 Thread Adrian Klaver
On 10/15/20 1:58 PM, Dirk Krautschick wrote: Hi, because of a migration from DB2 we have a lot of timestamps like -12-31-00.00.00.00 I'm assuming these got stored in a varchar field? What would be the best way to handle this in Postgres also related to overhead and performance (ind

Date Format 9999-12-31-00.00.00.000000

2020-10-15 Thread Dirk Krautschick
Hi, because of a migration from DB2 we have a lot of timestamps like -12-31-00.00.00.00 What would be the best way to handle this in Postgres also related to overhead and performance (index usage?). Or is TO_TIMESTAMP('-12-31-00.00.00.00', '-MM-DD-HH24.MI.SS.US') the only