Re: Issue with timestamp without time zone datatype with default value as now()/localtimestamp

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Deepika S Gowda <deepika(dot)gs(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org, pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Issue with timestamp without time zone datatype with default value as now()/localtimestamp
Date: 2020-07-10 14:09:00
Message-ID: 5f984784-fde3-9df1-0640-b099e82f13ff@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 7/10/20 7:03 AM, Deepika S Gowda wrote:
> Hi,
>
> On postgres 11.7 Master/Slave node, there is column named "createddate"
> with datatype "timestamp without time zone" with default value as "now()";
>
> Column Name | Date Type                 | Default value
> createddate |timestamp without time zone|Now()
>
>
> Issue: From the java application , data is getting loaded into this
> table where we expect column value should be today's date with
> timestamp( "2020-07-10 10:56:43.21"). But, out of 3K records, 100
> records are loaded as  "2019-07-10 10:56:43.21" (change in Year).
>
> What could be the issue? we tried changing the default value to
> "localtimestamp".

I would day the choices are:

1) A machine has it's clock set wrong.

2) The data is being loaded with a value for createdate that overrides
the DEFAULT.

>
> Kindly help on this request
>
> Regardss,
> Deepika

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Vishwa Kalyankar 2020-07-10 14:48:19 Re: Postgresql-12 taking more time to execute the query
Previous Message Deepika S Gowda 2020-07-10 14:03:19 Issue with timestamp without time zone datatype with default value as now()/localtimestamp