Re: 9.1 got really fast ;)

From: Alban Hertroys <haramrae(at)gmail(dot)com>
To: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
Cc: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org
Subject: Re: 9.1 got really fast ;)
Date: 2011-10-17 15:32:01
Message-ID: CAF-3MvMV+ts+xk5XU2WOc+KP4fxFeWuhjwaST58D4ZS-+jmiKg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 17 October 2011 17:25, Steve Crawford <scrawford(at)pinpointresearch(dot)com> wrote:
> On 10/16/2011 04:39 PM, Scott Marlowe wrote:
>>
>> On Sun, Oct 16, 2011 at 5:24 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us>  wrote:
>>>
>>> Scott Marlowe<scott(dot)marlowe(at)gmail(dot)com>  writes:
>>>>
>>>> On Sat, Oct 15, 2011 at 2:20 PM, Thomas Kellerer<spam_eater(at)gmx(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2011-10-17 15:33:16 Re: plpgsql; execute query inside exists
Previous Message Alban Hertroys 2011-10-17 15:28:44 Re: plpgsql; execute query inside exists