On 17 October 2011 17:25, Steve Crawford <scrawf...@pinpointresearch.com> wrote: > On 10/16/2011 04:39 PM, Scott Marlowe wrote: >> >> On Sun, Oct 16, 2011 at 5:24 PM, Tom Lane<t...@sss.pgh.pa.us> wrote: >>> >>> Scott Marlowe<scott.marl...@gmail.com> writes: >>>> >>>> On Sat, Oct 15, 2011 at 2:20 PM, Thomas Kellerer<spam_ea...@gmx.net> >>>> wrote: >>>>> >>>>> Total runtime: -2.368 ms<<==== this is amazing ;) >>>> >>>> I get something similar when I do select now()-query_start from >>>> pg_stat_activity on my Ubuntu 10.04 / pg 8.3 servers. >>> >>> Within a transaction block that's not surprising, because now() is >>> defined as transaction start time not statement start time. >> >> No transaction block. >> > Even stand-alone statements take place within a transaction - just not an > explicit one.
I doubt that more than 2.368 ms passed between the start of a transaction and the stand-alone statement it's wrapping though. Not impossible, but clock skew seems more likely to me. -- If you can't see the forest for the trees, Cut the trees and you'll see there is no forest. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general