Re: Hmmm... why does CPU-intensive pl/pgsql code parallelise so badly when queries parallelise fine? Anyone else seen this?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux