Constantine Peresypkin

I have successfully built a working plv8 on top of 8.8.278.14 right now. Yes, shit is crazy. I will try to submit PRs ASAP, so we won't do same things...

Added #426 #427 #428 Only the eval size check is omitted, can add it too for the sake of completeness

@JamesInform there are much more problems that you will need to solve then... Unfortunately `v8` is highly unstable in OOM conditions, even if it's an OOM in isolate only. I'm...

@ikalafat ``` cd plv8-2.3.14 DESTDIR=/tmp/plv8 make install && (cd /tmp/plv8; tar cvf /tmp/plv8-2.3.14.tar.gz .) tar tvf /tmp/plv8-2.3.14.tar.gz ```

> worst case scenario might be to stash the value somewhere, and use it, maybe even as part of the `plv8.start_proc` It's the best case scenario actually User role never...

> I guess, the start_proc will not work as expected in my case. AFAIK you're guessing wrong. It will switch context to the user, including correct globals. More than that,...

@speller > But I'm using AWS RDS... Then you will not benefit from any new plv8 features anyway. Essentially you need to create something for existing plv8 versions, because we...

@speller just FYI, there's a neat trick to get current user into any procedure without sacrificing security ```sql create domain "invoker" as name check (value = current_user); create function my_func...

@JerrySievert I think it's fixed in #441 too, but may need to add a specific tests for it (different compile flags). I have also added timeouts to compilation phase, otherwise...

Ah, that's a pretty peculiar case of `SPI_execute` with timeout. It seems like it's not covered. More than that after looking at the plpgsql code I have no idea how...