Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 6DB6C47603C for ; Mon, 23 Sep 2002 23:35:24 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id D3044475FF1 for ; Mon, 23 Sep 2002 23:35:23 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g8O3ZD5D009761; Mon, 23 Sep 2002 23:35:13 -0400 (EDT) To: Bruce Momjian Cc: josh@agliodbs.com, Manfred Koizar , Aaron Held , Roberto Mello , Neil Conway , pgsql-sql@postgresql.org Subject: Re: [GENERAL] CURRENT_TIMESTAMP In-reply-to: <200209240037.g8O0bwM14523@candle.pha.pa.us> References: <200209240037.g8O0bwM14523@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Mon, 23 Sep 2002 20:37:58 -0400" Date: Mon, 23 Sep 2002 23:35:13 -0400 Message-ID: <9760.1032838513@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/290 X-Sequence-Number: 9567 Bruce Momjian writes: > I was thinking 'transaction_timestamp' for the transaction start time, and > current_timestamp for the statement start time. I would equate now() > with current_timestamp. So you want to both (a) invent even more nonstandard syntax than we already have, and (b) break as many traditional-Postgres applications as you possibly can? 'transaction_timestamp' has no reason to live. It's not in the spec. And AFAIK the behavior of now() has been well-defined since the beginning of Postgres. If you want to change 'current_timestamp' to conform to a rather debatable reading of the spec, then fine --- but keep your hands off of now(). regards, tom lane