Received: from golem.fourpalms.org (www.fourpalms.org [64.3.68.148])
	by postgresql.org (8.11.3/8.11.4) with ESMTP id fAE78Zm72649
	for <pgsql-docs@postgresql.org>; Wed, 14 Nov 2001 02:08:35 -0500 (EST)
	(envelope-from lockhart@fourpalms.org)
Received: from fourpalms.org (localhost.localdomain [127.0.0.1])
	by golem.fourpalms.org (Postfix) with ESMTP
	id 8EF93FEC2; Wed, 14 Nov 2001 07:08:34 +0000 (UTC)
Message-ID: <3BF21872.F90FEB6A@fourpalms.org>
Date: Wed, 14 Nov 2001 07:08:34 +0000
From: Thomas Lockhart <lockhart@fourpalms.org>
Reply-To: lockhart@fourpalms.org
Organization: Yes
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.17-21mdksmp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>,
	PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: Use of 'now'
References: <200111140246.fAE2kWE17608@candle.pha.pa.us>
	<4638.1005706352@sss.pgh.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200111/31
X-Sequence-Number: 1104

...
> 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?

Not sure where "supposed to" came from ;)

Previous versions of PostgreSQL can and will generate dump files which
have 'current'. I did make it equivalent to 'now' for at least the 7.2
series of releases.

                     - Thomas