pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Andomar <andomar@aule.net>
To: pgsql-performance@postgresql.org
Subject: Re: Query plan with missing timespans
Date: Wed, 22 Apr 2015 21:59:27 +0200
Message-ID: <5537FD9F.3060109@aule.net> (raw)
In-Reply-To: <223706913.2307849.1429732023067.JavaMail.yahoo@mail.yahoo.com>
References: <5537DC6D.2010300@aule.net>
	<223706913.2307849.1429732023067.JavaMail.yahoo@mail.yahoo.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

> 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

view thread (5+ messages)  latest in thread

Message-ID: <5537FD9F.3060109@aule.net>
Permalink:  ../5537FD9F.3060109@aule.net/
Also on:    postgresql.org/message-id/5537FD9F.3060109@aule.net

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: andomar@aule.net
  Subject: Re: Query plan with missing timespans
  In-Reply-To: <5537FD9F.3060109@aule.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox