remote debugger: FATAL: BeginInternalSubTransaction: unexpected state DEFAULT

[GoogleCodeExporter]

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)
FATAL:  BeginInternalSubTransaction: unexpected state DEFAULT

What version of the product are you using? On what operating system?
plv8 1.3.0, pg 9.2.2 OS X 10.8.2

googled it and found: 
http://postgresql.1045698.n5.nabble.com/backend-crash-with-FATAL-BeginInternalSu
bTransaction-unexpected-state-END-td2123467.html

Beyond my debugging skills, but I guess because I'm not in an sql function than 
the current transaction is in a non-supported state.  I tried to 
plv8.execute("BEGIN") but that didn't help either.

Original issue reported on code.google.com by t...@blit.com on 15 Jan 2013 at 7:38

[GoogleCodeExporter]

I cannot reproduce it.

do $$ plv8.execute('select 1==1'); $$ language plv8;
ERROR:  Error: operator does not exist: integer == integer
DETAIL:  undefined() LINE 1:  plv8.execute('select 1==1'); 

Can you provide a complete repro?

Original comment by umi.tan...@gmail.com on 28 Feb 2013 at 10:02

[GoogleCodeExporter]

the crash happens when calling plv8.execute from the d8 console (to debug a 
stored proc)

Original comment by t...@blit.com on 28 Feb 2013 at 10:36

[GoogleCodeExporter]

I see.  It seems there is only little we can do because it is quite a bit of 
work to get into a transaction state from scratch, as in d8 debugger state, so 
I'd make it an error.

Original comment by umi.tan...@gmail.com on 1 Mar 2013 at 12:29

[GoogleCodeExporter]

Committed a few lines to avoid the crash.  Thanks for the report.

Original comment by umi.tan...@gmail.com on 9 Apr 2013 at 7:31

• Changed state: Fixed