Message-ID: <5537FD9F.3060109@aule.net>
Date: Wed, 22 Apr 2015 21:59:27 +0200
From: Andomar <andomar@aule.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
 rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
Subject: Re: Query plan with missing timespans
References: <5537DC6D.2010300@aule.net>
 <223706913.2307849.1429732023067.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <223706913.2307849.1429732023067.JavaMail.yahoo@mail.yahoo.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

> Looping through 384 index scans of tbl, each taking 0.040 ms.
> That's 15.36 ms.  That leaves 0.291 ms unaccounted for, which means
> that's about how much time the top level nested loop took to do its
> work.
>

Thanks for your reply, interesting!  I'd have thought that this line 
actually implied 0 ms:

     actual time=0.040..0.040

But based on your reply this means, it took between 0.040 and 0.040 ms 
for each loop?

Is there a way to tell postgres that a function will always return the 
same result for the same parameter, within the same transaction?

Kind regards,
Andomar


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance