From: | Christoph Haller <ch(at)rodos(dot)fzk(dot)de> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: [GENERAL] CURRENT_TIMESTAMP |
Date: | 2002-09-24 12:08:29 |
Message-ID: | 3D9055BD.5AA86176@rodos.fzk.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
>
> 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(at)candle(dot)pha(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-09-24 13:26:25 | Re: [GENERAL] CURRENT_TIMESTAMP |
Previous Message | Haller Christoph | 2002-09-24 11:44:47 | Re: [GENERAL] CURRENT_TIMESTAMP |