Re: query not scaling

From: Rob Sargent <robjsargent(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: query not scaling
Date: 2017-10-26 15:17:49
Message-ID: 857d59d2-bf2a-a595-7fcc-9b35fa3fb86a@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/26/2017 09:01 AM, Tom Lane wrote:
> Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
>> Also, to have PostgreSQL inline the function, which would be good
>> for performance, it should be declared IMMUTABLE.
> Actually, if you hope to have a SQL function be inlined, it's better
> not to decorate it at all --- not with IMMUTABLE, and not with STRICT
> either. Both of those restrict the parser's ability to inline unless
> it can prove the contained expression is equally immutable/strict.
> With the default attributes of volatile/not strict, there's nothing
> to prove.
>
> (In any case, it's usually easy enough to tell from EXPLAIN output
> whether inlining has happened.)
>
> regards, tom lane
As to the explain analyze,

could not receive data from server: Connection timed out
Time: 7877340.565 ms

for the second time. I had presumed at first that this had occurred
during a network burp. I'll try running it directly on the pg host.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Zhu, Joshua 2017-10-26 17:15:05 BDR question on dboid conflicts
Previous Message Tom Lane 2017-10-26 15:01:27 Re: query not scaling