Hi Dave, make sense. We should ensure that operations happen sequentially. Please find attached patch file for the fix.
Thanks, Neel Patel On Sat, Jun 18, 2016 at 8:40 PM, Dave Page <dp...@pgadmin.org> wrote: > Hi > > Isn't any solution that relies on artificial delays likely to fail sooner > or later? Can't we reliably ensure the operations happen sequentially? > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK:http://www.enterprisedb.com > The Enterprise PostgreSQL Company > > On 18 Jun 2016, at 11:43, Neel Patel <neel.pa...@enterprisedb.com> wrote: > > Hi, > > Please find attached patch file for the fix of RM #1354 and RM #1323. > > RM 1354 - Debugging PL/pgSQL causes "Debugger: Error fetching variable > information". > > RM 1323 - Debugger: Continue execution error displayed if debug plpgsql > function in Desktop Runtime Application. > > Both the issue are related. Below are the issue description and solution. > > *Issue :- * > > We are getting error of "fetching variable information" and "execution > error" because as one query is already in state of execution and at the > same time without getting its result we are sending another query to fetch > the variable and stack information and due to that we are getting the error. > > *Solution:-* > > We should give enough time for execution query to finish its operation and > then we should get the function debug information like variable info, stack > info, breakpoint info etc. > > Do review it and let us know for comments. > > Thanks, > Neel Patel > > <RM_1354_1323.patch> > > > -- > Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-hackers > >
RM_1354_1323_v2.patch
Description: Binary data
-- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers
