pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: borratejaabhi@gmail.com
Subject: BUG #16240: The now() function is populating different date time than expected
Date: Mon, 03 Feb 2020 10:38:10 +0000
Message-ID: <16240-81d13113beecf3cb@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      16240
Logged by:          Abhishek Borra
Email address:      borratejaabhi@gmail.com
PostgreSQL version: 9.6.9
Operating system:   Linux
Description:        

We have certain columns in our database of data type 'timestamp with time
zone'. We are populating them with now() function as default value
.Sometimes the date time is getting populated as dates from 2017/18
randomly. What can be the possible cause of this issue?



view thread (2+ messages)  latest in thread

Message-ID: <16240-81d13113beecf3cb@postgresql.org>
Permalink:  ../16240-81d13113beecf3cb@postgresql.org/
Also on:    postgresql.org/message-id/16240-81d13113beecf3cb@postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, borratejaabhi@gmail.com
  Subject: Re: BUG #16240: The now() function is populating different date time than expected
  In-Reply-To: <16240-81d13113beecf3cb@postgresql.org>
  References: <16240-81d13113beecf3cb@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox