Message-ID: <520B000C.2030104@2ndquadrant.com>
Date: Wed, 14 Aug 2013 11:57:00 +0800
From: Craig Ringer <craig@2ndquadrant.com>
Organization: 2nd Quadrant
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: Pavel Stehule <pavel.stehule@gmail.com>
CC: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: Interesting case of IMMUTABLE significantly hurting
 performance
References: <520AD240.9060508@2ndquadrant.com>
 <CAFj8pRBF3Qr7WtQwO1H_WN=hhFGk0semwhdE+ODz3iyv-TroMQ@mail.gmail.com>
In-Reply-To: 
 <CAFj8pRBF3Qr7WtQwO1H_WN=hhFGk0semwhdE+ODz3iyv-TroMQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

On 08/14/2013 11:52 AM, Pavel Stehule wrote:
> 
> If I understand, a used IMMUTABLE flag disables inlining. What you see,
> is SQL eval overflow.
> 
> My rule is - don't use flags in SQL functions, when it is possible.

Interesting. I knew that was the case for STRICT, but am surprised to
hear it's the case for IMMUTABLE as well. That seems ...
counter-intuitive. Not to mention undocumented as far as I can see.

-- 
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


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