Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fAE2kXm66435 for ; Tue, 13 Nov 2001 21:46:33 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id fAE2kWE17608; Tue, 13 Nov 2001 21:46:32 -0500 (EST) From: Bruce Momjian Message-Id: <200111140246.fAE2kWE17608@candle.pha.pa.us> Subject: Re: Use of 'now' In-Reply-To: <4537.1005704839@sss.pgh.pa.us> "from Tom Lane at Nov 13, 2001 09:27:19 pm" To: Tom Lane Date: Tue, 13 Nov 2001 21:46:32 -0500 (EST) CC: PostgreSQL-documentation X-Mailer: ELM [version 2.4ME+ PL90 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200111/26 X-Sequence-Number: 1099 > Bruce Momjian writes: > > This seems wrong to me. What does it mean when it says 'current' is > > resolved every time the value is retrieved? > > Nothing of interest anymore, since 'current' has been removed as of 7.2. > However, Thomas has yet to commit any docs updates for his recent > datetime-related changes ... including that one ... Seems it is still in there somewhere: test=> create table bb (x timestamp default 'current', y int); CREATE test=> insert into bb (y) values (1); INSERT 16591 1 test=> select * from bb; x | y -------------------------------+--- 2001-11-13 21:45:22.473896-05 | 1 (1 row) Do you mean that 'current' is now the same as 'now'? :-) -- 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