Hi,
thanks for your help which already resolved the issue for me. I worked through
your replies and it is indeed a startup delay for the first call to a plv8
function in a session. I pasted the query plans below for comparison.
```
explain analyze select normalizeunidiff('')
On 24 March 2018 at 14:35, Andres Freund wrote:
> How long does planning take if you repeat this? I wonder if a good chunk
> of those 1.8s is initial loading of plv8.
Maybe, but it also could be the execution of the function, after all,
the planner does invoke immutable functions:
# explain verb
Hi,
On 2018-03-23 21:28:22 +0100, b...@e8s.de wrote:
> I have a table api.issues that has a text column "body" with long texts
> (1000+ chars). I also wrote a custom function "normalizeBody" with plv8 that
> is a simple Text -> Text conversion. Now I created an index applying the
> function to
