Re: Why overhead of SPI is so large?

From: Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why overhead of SPI is so large?
Date: 2019-11-22 08:15:51
Message-ID: 625ac42b-1610-460a-8644-072e5da1314e@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22.11.2019 11:05, Pavel Stehule wrote:
>
>
> We should to distinguish  between bad result and not well optimized plan.
>
If it is not possible to implement runtime check tha timmutable function
is not making any changes in database.
Please notice, that even right now without any get snapshot optimization
Postgres can produce incorrect result in case of incorrectly specidied
immutable or stable qualifiers.

--
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Juan José Santamaría Flecha 2019-11-22 08:55:46 Re: TAP tests aren't using the magic words for Windows file access
Previous Message Michael Paquier 2019-11-22 08:07:36 Re: add a MAC check for TRUNCATE