Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 680BB4763FC for ; Tue, 24 Sep 2002 08:08:29 -0400 (EDT) Received: from fzkmail2.fzk.de (fzkmail2.fzk.de [141.52.27.52]) by postgresql.org (Postfix) with SMTP id EA6FB475B8A for ; Tue, 24 Sep 2002 08:08:27 -0400 (EDT) Received: FROM resy5.fzk.de BY fzkmail2.fzk.de ; Tue Sep 24 14:08:30 2002 +0200 Received: œby rodos.fzk.de with ESMTP (8.8.6 (PHNE_17135)/8.7.1) id OAA19060 for ; Tue, 24 Sep 2002 14:08:29 +0200 (METDST) Message-ID: <3D9055BD.5AA86176@rodos.fzk.de> Date: Tue, 24 Sep 2002 14:08:29 +0200 From: Christoph Haller X-Mailer: Mozilla 4.06 [en] (X11; I; HP-UX B.10.20 9000/780) MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: Re: [GENERAL] CURRENT_TIMESTAMP Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/298 X-Sequence-Number: 9575 > > 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