From: Haller Christoph <Christoph.Haller@rodos.fzk.de>
To: pgsql-sql@postgresql.org
Subject: Re: [GENERAL] CURRENT_TIMESTAMP
Date: Tue, 24 Sep 2002 13:44:47 +0200
Message-ID: <3D90502E.75FD9B9@rodos.fzk.de> (raw)
>
> Christoph Haller wrote:
> > Hi pgsql-sql list,
> > I did some testing around tables using a column
> > timestamp with time zone not null default now().
> > I have noticed a valuable feature:
> > As long as being inside a transaction initiated by
> > begin;
> > the return value of the now() function does not change.
> > Is this intended - as written in the documentation?
> > Can I rely on it, so future releases of PostgreSQL
> > will act the same.
>
> Yes, this is intended and will not change.
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania
19026
>
I vote the now() behaviour not to change.
Regards, Christoph
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: Christoph.Haller@rodos.fzk.de
Subject: Re: [GENERAL] CURRENT_TIMESTAMP
In-Reply-To: <3D90502E.75FD9B9@rodos.fzk.de>
* 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