Postgres Pro
Downloads
Home   >   mailing lists

Re: Why overhead of SPI is so large? - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Why overhead of SPI is so large?
Date
Msg-id CAFj8pRDudG=L1GcnmnHbTHG=L_Hxm7NnG_hty0irjMMD_67nKg@mail.gmail.com
Whole thread Raw
In response to Re: Why overhead of SPI is so large?  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Responses Re: Why overhead of SPI is so large?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view


čt 21. 11. 2019 v 10:31 odesílatel Konstantin Knizhnik <k.knizhnik@postgrespro.ru> napsal:

> I've set the CF entry to "Waiting on Author" pending a new patch
> that does it like that.

With contain_mutable_functions the patch becomes trivial.

Stable functions doesn't need own snapshot too, so it is not fully correct, but it is on safe side.

Pavel


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

pgsql-hackers by date:

Previous
From: Nikolay Shaplov
Date:
Subject: Re: [PATCH] Do not use StdRdOptions in Access Methods
Next
From: Pavel Stehule
Date:
Subject: obsolete example