Re: Timezone information

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com>
Cc: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Timezone information
Date: 2014-02-20 16:00:05
Message-ID: 53062685.8040000@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 02/20/2014 04:59 AM, Dev Kumkar wrote:
> On Thu, Feb 20, 2014 at 4:31 AM, Adrian Klaver
> <adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>> wrote:
>
> It depends on how you are declaring the timestamp field. If you do
> not use with time zone then the input value is open to
> interpretation and is not 'anchored' to a point in time.
>
> Example
>
> My time zone is currently PST.
> test=> create table timestamp_test(id int, ts timestamp, ts_z
> timestamp with time zone);
> CREATE TABLE
> test=> insert into timestamp_test values (1, now(), now());
> INSERT 0 1
> .....
> If you know what time zone the value was inserted under you can get
> it back.
> .
> .
> That assumes a lot, so the best thing is to use timestamp with time
> zone.
>
>
> Thanks for trying this out on your setup. However looks like my
> requirement is different here.

So what is your requirement?
Do you have a specific application/use for the databases you are installing?

>
> Regards...

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Luz_Diaz 2014-02-20 16:04:27 FIPS mode - SSL connection fails and RAND_cleanup
Previous Message Adrian Klaver 2014-02-20 15:57:43 Re: Timezone information