Re: EPOCH time vs PG timestamp

From: Sam Barnett-Cormack <s(dot)barnett-cormack(at)lancaster(dot)ac(dot)uk>
To: Louie Kwan <lkwan(at)nuvo(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: EPOCH time vs PG timestamp
Date: 2004-03-10 19:31:15
Message-ID: Pine.LNX.4.58.0403101930410.13570@short.lancs.ac.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

The PG timestamp has the advantage of actually being able to cover any
time, and be timezone-aware if you wish.

Epoch time, obviously, is more constrained.

On Wed, 10 Mar 2004, Louie Kwan wrote:

> Hi All,
>
> I am doing a data warehouse project using postgresql and I need warehousing
> data from different operational systems, like, Remedy and NNM, etc...
>
> Some data is time sensetive, I am thinking to use epoch as the format of the
> time instead of Postgre Timestamp data type !!
>
> The challenge for me is that different operational systems are using
> different data format, for example, Remedy is using epoch time and NNM has
> it own format.. when I do ETL ... I think I need to choose a time format and
> I may prefer to use epoch time.
>
> Any comment or any experience ?
>
> Thanks in advance.
>
> Best regards,
> Louie Kwan
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>

--

Sam Barnett-Cormack
Software Developer | Student of Physics & Maths
UK Mirror Service (http://www.mirror.ac.uk) | Lancaster University

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Vivek Khera 2004-03-10 21:00:36 Re: syslog slowing the database?
Previous Message Mark Harrison 2004-03-10 19:08:50 Re: syslog slowing the database?