Jerry Sievert
Jerry Sievert
I won't be able to work on it until next weekend, so I'm still at least a week away from a new release, but I will also try to solve...
3.1 has been released. while it does not solve the universal binary issue, it does work well on arm64 and amd64
I would happily accept a doc pr for the contrib doc files with a link and info about this and rebuild the Github.Io page.
the current user/role is not exposed at this time. plv8 technically has access to the `Oid` via `GetUserId()` but to map that to a role name, it too would need...
> I'm using a trigger to assign an ACL list to a new row on INSERT commands. ah, I see. as @pkit noted, changing roles changes context for plv8 as...
unfortunately, even plv8 would need to query to get a lot of that information in a clean, API agnostic way. most of that information is stored in Postgres's table-structure.
as mentioned before, plv8 has access to the internal numerically mapped role id via `GetUserId()` which is an internal, not guaranteed to be stable function deep inside postgres itself. plv8...
amazon tends to update minor versions fairly quickly - that said, even if a new feature *were* back ported to a minor version (bug fixes are), then it would be...
thanks for the report! I'll take a look at it as soon as I can.
I am unable to reproduce your (latest) issue @jngbng, can you please report which version of plv8 and which version of Postgres you are seeing this in?