-
```
What steps will reproduce the problem?
1. connect to plv8 with d8: /d8 --remote-debugger --debugger_port=35432
2. issue any sql statement: plv8.execute("select 1==1");
result: (pg backend crash)…
-
```
What steps will reproduce the problem?
Make installcheck
What is the expected output? What do you see instead?
instead of success, this failure:
*** /home/andrew/plv8js/expected/plv8.out 2…
-
```
It looks like this [1] change that allows varargs-style arguments to
plv8.execute may have an off-by-one error?
Passing in an array still works as expected:
d7l4hfvukuffq4=# do 'plv8.elog(NOTIC…
-
```
What steps will reproduce the problem?
1. build v8
2. build plv8js
3. create extension plv8; on postgres
What is the expected output? What do you see instead?
Should successfully create extensi…
-
```
What steps will reproduce the problem?
1. brew install v8
2. make install
3.
What is the expected output? What do you see instead?
g++ -O2 -pthread -Wall -Wmissing-prototypes -Wpointer-arith
-Wd…
-
```
What steps will reproduce the problem?
returning a value from a try/catch with a js error works as expected, however
if the error is caused by postgres, returning a value crashes the server. To…
-
```
What steps will reproduce the problem?
1. I am compiling with mingw-w64 chain
2. Did a git clone -b r1.4 https://code.google.com/p/plv8js/ plv8js
3. Compiled as usual except pointing at my 9.3 dev…
-
```
This might not be a bug, but I'm having a rough go with type coercion errors so
hopefully this can be fixed.
summary: (id is type integer)
plv8.execute("select * from typetest where id = '1'") …
-
```
What steps will reproduce the problem?
1. Create a table with a field of type "date" and a couple of records.
2. Select that field from the table manually in psql.
3. Run plv8.execute('SELECT dat…
-
```
Can't call functions from plv8.start_proc under other user than postgres
Set up startup procedure in config
plv8.start_proc = 'plv8_startup'
Created function:
CREATE OR REPLACE FUNCTION plv8_s…