From: Thomas Lockhart <lockhart@fourpalms.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: Use of 'now'
Date: Wed, 14 Nov 2001 07:08:34 +0000
Message-ID: <3BF21872.F90FEB6A@fourpalms.org> (raw)
References: <200111140246.fAE2kWE17608@candle.pha.pa.us>
<4638.1005706352@sss.pgh.pa.us>
...
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: lockhart@fourpalms.org, tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us
Subject: Re: Use of 'now'
In-Reply-To: <3BF21872.F90FEB6A@fourpalms.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox