Re: Negative result with (now()-previously_inserted_timestamp)

On Wed, Jul 7, 2010 at 12:18 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Gurjeet Singh <singh.gurjeet@gmail.com> writes:
> > I ran the following query, and got an unexpected negative value. Does
> this
> > imply that SELECT-transaction was able to see a row created by
> > INSERT-transaction which started after the SELECT-transaction?
>
> Was the SELECT inside a BEGIN block?
>

No. I have the psql session still open so can confirm that with absolute
confidence.

If you must know, this instance is on a low-cost, hosted, Xen virtual
machine.

By any chance, can we suspect the timer accuracy here? Or possibly an NTP
server foul-play!

Regards,
--
gurjeet.singh
@ EnterpriseDB - The Enterprise Postgres Company
http://www.EnterpriseDB.com

singh.gurjeet@{ gmail | yahoo }.com
Twitter/Skype: singh_gurjeet

Mail sent from my BlackLaptop device