From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: Martijn van Oosterhout <kleptog@svana.org>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Manfred Koizar <mkoi-pg@aon.at>
Cc: Roland Roberts <roland@astrofoto.org>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-general@postgresql.org
Subject: Re: [SQL] CURRENT_TIMESTAMP
Date: Sun, 29 Sep 2002 23:53:59 -0400
Message-ID: <14617.1033358039@sss.pgh.pa.us> (raw)
In-Reply-To: <200209291243.45747.josh@agliodbs.com>
References: <20020929034706.GA6199@svana.org>
<20020929041007.GB6199@svana.org>
<8140.1033274153@sss.pgh.pa.us>
<200209291243.45747.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> Are we still planning on putting the three different versions of now() on the
> TODO? I.e.,
> now('transaction'),
> now('statement'), and
> now('immediate')
> With now() = now('transaction')?
I have no objection to doing that. What seems to be contentious is
whether we should change the current behavior of CURRENT_TIMESTAMP.
regards, tom lane
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, kleptog@svana.org, pgman@candle.pha.pa.us, mkoi-pg@aon.at, roland@astrofoto.org, pgsql-general@postgresql.org
Subject: Re: [SQL] CURRENT_TIMESTAMP
In-Reply-To: <14617.1033358039@sss.pgh.pa.us>
* 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