Horton

Re: [GENERAL] CURRENT_TIMESTAMP

Manfred Koizar <mkoi-pg@aon.at>

View thread View on postgr.es
From: Manfred Koizar <mkoi-pg@aon.at>
To: josh@agliodbs.com
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Bruce Momjian <pgman@candle.pha.pa.us>, Aaron Held <aaron@MetroNY.com>, Roberto Mello <rmello@cc.usu.edu>, Neil Conway <neilc@samurai.com>, pgsql-sql@postgresql.org
Date: 2002-09-24T09:16:20Z
Lists: pgsql-hackers, pgsql-general, pgsql-sql 
On Mon, 23 Sep 2002 13:36:59 -0700, Josh Berkus <josh@agliodbs.com>
wrote:
>I, for one, would judge that the start time of the statement is "during the 
>execution"; it would only NOT be "during the execution" if it was a value 
>*before* the start time of the statement.  It's a semantic argument.

Josh, you're right, I meant closed interval.

>Further, we could not change that behaviour without breaking many people's 
>applications.
>
>Ideally, since we get this question a lot, that a compile-time or 
>execution-time switch to change the behavior of current_timestamp 
>contextually would be nice.

Yes, GUC!

>We just need someone who;s interested enough in 
>writing one.

First we need someone who decyphers SQL99's wording.

Servus
 Manfred