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

help / color / mirror / Atom feed
From: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-performance@postgresql.org
Subject: Re: Hmmm... why does CPU-intensive pl/pgsql code parallelise so badly when queries parallelise fine? Anyone else seen this?
Date: Thu, 09 Jul 2015 15:22:10 +0200
Message-ID: <mnlsi2$oh8$1@ger.gmane.org> (raw)
In-Reply-To: <14796976-FF86-4A4D-97EE-259FCC9D01CF@skogoglandskap.no>
References: <6E55113B-FA05-433C-9B21-623F798EE935@skogoglandskap.no>
	<CAFwQ8rcEOiGJ79WtoO=uTX33ZhKVUWG9v8iO14TR+AoT_wd1og@mail.gmail.com>
	<559CB5BF.2080509@commandprompt.com>
	<CAFwQ8rdWcZwUxgQDySOzFAqHJPm6=DVH+bp0XMJzmADF1GVmPw@mail.gmail.com>
	<CAHyXU0wO_WMzrbdcdtWwpk-78j_4P-M-Kr0xOyJVg1K15dQNAQ@mail.gmail.com>
	<20150708202733.GS10242@alap3.anarazel.de>
	<CAFwQ8rcmN5APWKS8v9JBqvQ8_x2by276LFBZxtci-32BnuMGUg@mail.gmail.com>
	<20150708224518.GT10242@alap3.anarazel.de>
	<15702.1436413118@sss.pgh.pa.us>
	<14796976-FF86-4A4D-97EE-259FCC9D01CF@skogoglandskap.no>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

Graeme B. Bell schrieb am 09.07.2015 um 11:44:
> I don't recall seeing a clear statement telling me I should mark pl/pgsql
> functions nonvolatile wherever possible or throw all performance and
> scalability out the window. 

From: http://www.postgresql.org/docs/current/static/xfunc-volatility.html

   "For best optimization results, you should label your functions 
    with the strictest volatility category that is valid for them."





-- 
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 (23+ messages)  latest in thread

Message-ID: <mnlsi2$oh8$1@ger.gmane.org>
Permalink:  ../mnlsi2$oh8$1@ger.gmane.org/
Also on:    postgresql.org/message-id/mnlsi2$oh8$1@ger.gmane.org

 · 

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: spam_eater@gmx.net
  Subject: Re: Hmmm... why does CPU-intensive pl/pgsql code parallelise so badly when queries parallelise fine? Anyone else seen this?
  In-Reply-To: <mnlsi2$oh8$1@ger.gmane.org>

* 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