From: Adrian Klaver <aklaver@comcast.net>
To: pgsql-sql@postgresql.org
Cc: luke.78@libero.it
Subject: Re: Problem with now() in function pgsql
Date: Sat, 5 Apr 2008 10:59:51 -0700
Message-ID: <200804051059.51195.aklaver@comcast.net> (raw)
In-Reply-To: <JYV5E7$EC8D8702500FEA2AF450CE088A16C723@libero.it>
References: <JYV5E7$EC8D8702500FEA2AF450CE088A16C723@libero.it>
On Saturday 05 April 2008 10:46 am, luke.78@libero.it wrote:
> Hi,
> I have a problem in a function pgsql with Reading TIMESTAMP calling the
> function now() the problem is this:
> At the begin of function I read timestamp...
> select now() into TS_BEGIN;
>
> the function execute some statement...
>
> Many seconds after I reread the timestamp
> select now() into TS_END;
>
> and TS_BEGIN is identical TS_END!!!
>
> Can anyone help me?
>
> Thanks in advance.
>
> Luke.
You want to use clock_timestamp() or equivalent not now(). As you found out
now() fixes the time at the start of the transaction and does not change,
clock_timestamp() does. See URL below for a more complete explanation:
http://www.postgresql.org/docs/8.2/interactive/functions-datetime.html
--
Adrian Klaver
aklaver@comcast.net
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: aklaver@comcast.net, luke.78@libero.it
Subject: Re: Problem with now() in function pgsql
In-Reply-To: <200804051059.51195.aklaver@comcast.net>
* 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