pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jean-Luc Lachance <jllachan@nsd.ca>
To: josh@agliodbs.com, Tom Lane <tgl@sss.pgh.pa.us>
To: Martijn van Oosterhout <kleptog@svana.org>
To: Bruce Momjian <pgman@candle.pha.pa.us>
To: Manfred Koizar <mkoi-pg@aon.at>
To: Roland Roberts <roland@astrofoto.org>
To: pgsql-sql@postgresql.org
To: pgsql-general@postgresql.org
Subject: Re: [SQL] CURRENT_TIMESTAMP
Date: Mon, 30 Sep 2002 14:47:15 -0400
Message-ID: <3D989C33.D4ED849D@nsd.ca> (raw)
References: <20020929034706.GA6199@svana.org>
	<20020929041007.GB6199@svana.org>
	<8140.1033274153@sss.pgh.pa.us>
	<200209291243.45747.josh@agliodbs.com>
	<3D9899F9.72BD773A@nsd.ca>

OK, forget system_clock() or clock() timeofday() will do.


Jean-Luc Lachance wrote:
> 
> How can you make a difference between now('statement'), and
> now('immediate').
> To me they are the same thing. Why not simply now() for transaction, and
> now('CLOCK') or better yet system_clock() or clock() for curent time.
> 
> JLL



view thread (61+ messages)  latest in thread

Message-ID: <3D989C33.D4ED849D@nsd.ca>
Permalink:  ../3D989C33.D4ED849D@nsd.ca/
Also on:    postgresql.org/message-id/3D989C33.D4ED849D@nsd.ca

 · 

reply

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: jllachan@nsd.ca, tgl@sss.pgh.pa.us, 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: <3D989C33.D4ED849D@nsd.ca>

* 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