Re: Anomalies with the now() function - Mailing list pgsql-general

From David Roussel
Subject Re: Anomalies with the now() function
Date
Msg-id 8E62D326-D0D9-4863-9D56-C811DDF6818A@xsmail.com
Whole thread Raw
In response to Anomalies with the now() function  (Byrne Kevin-kbyrne01 <kbyrne01@motorola.com>)
List pgsql-general
I don't know about this particular problem, but I find in programming
in general it's always best to pass in the value of now as a
parameter, and pass it on to functions you are calling, thus avoiding
problems with mismatching values.

But as Andreas says the values should be the same within the same
transaction, at least that's what I thought.

David

pgsql-general by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: Sun supporting PostgreSQL
Next
From: Ben Martin
Date:
Subject: Custom GIST getting ERROR: too many LWLocks taken