Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fAE2qam66542 for ; Tue, 13 Nov 2001 21:52:37 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id fAE2qWc04641; Tue, 13 Nov 2001 21:52:32 -0500 (EST) To: Bruce Momjian , Thomas Lockhart cc: PostgreSQL-documentation Subject: Re: Use of 'now' In-reply-to: <200111140246.fAE2kWE17608@candle.pha.pa.us> References: <200111140246.fAE2kWE17608@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Tue, 13 Nov 2001 21:46:32 -0500" Date: Tue, 13 Nov 2001 21:52:32 -0500 Message-ID: <4638.1005706352@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200111/25 X-Sequence-Number: 1098 Bruce Momjian writes: >> 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); Hmm. It was *supposed* to be removed entirely, but possibly what Thomas actually did was to continue to accept the keyword as equivalent to 'now'. Thomas? regards, tom lane