Thread: plpgsql debugger (pldbg) absent from 8.4?
On the 2009-01-01 win32 release, I noticed I could no longer debug, like when I'd set a breakpoint I'd immediately get the error message: syntax error at or near "," LINE 1: SELECT * FROM pldbg_set_global_breakpoint(, 55208, NULL, NUL... ...and the output pane of the debugger would show: row number 0 is out of range 0..-1 Now, I noticed that pldbg.sql was not actually included (even though lib/pldbgapi.dll and lib/plugins/plugin_debugger.dll are), and I had been using the one from 8.3 to set it up. I also noticed that for the function from the error message it just calls a C function, so I seem to have no way of working around it with just the .SQL file. Does anybody have this working on their system? I hope in the final 8.4 at least that this feature is included again, because I find it extremely handy.
On Fri, Mar 13, 2009 at 1:19 PM, Kev <kevinjamesfield@gmail.com> wrote: > On the 2009-01-01 win32 release, I noticed I could no longer debug, > like when I'd set a breakpoint I'd immediately get the error message: > > syntax error at or near "," > LINE 1: SELECT * FROM pldbg_set_global_breakpoint(, 55208, NULL, > NUL... > > ...and the output pane of the debugger would show: > > row number 0 is out of range 0..-1 > > Now, I noticed that pldbg.sql was not actually included (even though > lib/pldbgapi.dll and lib/plugins/plugin_debugger.dll are), and I had > been using the one from 8.3 to set it up. I also noticed that for the > function from the error message it just calls a C function, so I seem > to have no way of working around it with just the .SQL file. > > Does anybody have this working on their system? I hope in the final > 8.4 at least that this feature is included again, because I find it > extremely handy. Temporary bug that's since been resolved. Sorry 'bout that. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Mar 13, 9:30 am, dp...@pgadmin.org (Dave Page) wrote: > On Fri, Mar 13, 2009 at 1:19 PM, Kev <kevinjamesfi...@gmail.com> wrote: > > On the 2009-01-01 win32 release, I noticed I could no longer debug, > > Temporary bug that's since been resolved. Sorry 'bout that. Oh, no worries, thanks for the reply. I notice there's no periodic build since then, but the nightly build link at http://www.postgresql.org/developer/testing doesn't seem to be up to much. Do you know if there's another periodic due before the official release?
On Fri, Mar 13, 2009 at 1:44 PM, Kev <kevinjamesfield@gmail.com> wrote: > On Mar 13, 9:30 am, dp...@pgadmin.org (Dave Page) wrote: >> On Fri, Mar 13, 2009 at 1:19 PM, Kev <kevinjamesfi...@gmail.com> wrote: >> > On the 2009-01-01 win32 release, I noticed I could no longer debug, >> >> Temporary bug that's since been resolved. Sorry 'bout that. > > Oh, no worries, thanks for the reply. I notice there's no periodic > build since then, but the nightly build link at http://www.postgresql.org/developer/testing > doesn't seem to be up to much. Do you know if there's another > periodic due before the official release? I'll see if I can get an updated build pushed out sometime today. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
> I'll see if I can get an updated build pushed out sometime today. I finally got around to trying this out using the March 24th build, and it has the same issue... Kev
On Wed, Apr 8, 2009 at 2:48 PM, Kevin Field <kevinjamesfield@gmail.com> wrote: >> I'll see if I can get an updated build pushed out sometime today. > > I finally got around to trying this out using the March 24th build, > and it has the same issue... I just installed it here on a clean VM and I see the docs, the SQL script and all the right libraries. What are you missing? -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Apr 8, 10:32 am, dp...@pgadmin.org (Dave Page) wrote: > On Wed, Apr 8, 2009 at 2:48 PM, Kevin Field <kevinjamesfi...@gmail.com> wrote: > >> I'll see if I can get an updated build pushed out sometime today. > > > I finally got around to trying this out using the March 24th build, > > and it has the same issue... > > I just installed it here on a clean VM and I see the docs, the SQL > script and all the right libraries. What are you missing? Well, the 2 DLLs are there, and actually, the SQL file is too, so I ran it, and it complained about types already existing, so I took out each of those and retried until all that were left were the CREATE OR REPLACE FUNCTION lines, and those ran successfully. But then I got the same error again when actually trying to do "Set Breakpoint" in pgAdmin. What else would I check for?
On Wed, Apr 8, 2009 at 3:47 PM, Kevin Field <kevinjamesfield@gmail.com> wrote: > On Apr 8, 10:32 am, dp...@pgadmin.org (Dave Page) wrote: >> On Wed, Apr 8, 2009 at 2:48 PM, Kevin Field <kevinjamesfi...@gmail.com> wrote: >> >> I'll see if I can get an updated build pushed out sometime today. >> >> > I finally got around to trying this out using the March 24th build, >> > and it has the same issue... >> >> I just installed it here on a clean VM and I see the docs, the SQL >> script and all the right libraries. What are you missing? > > Well, the 2 DLLs are there, and actually, the SQL file is too, so I > ran it, and it complained about types already existing, so I took out > each of those and retried until all that were left were the CREATE OR > REPLACE FUNCTION lines, and those ran successfully. But then I got > the same error again when actually trying to do "Set Breakpoint" in > pgAdmin. What else would I check for? Did you add shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' to postgresql.conf and restart the server per the README? -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Apr 8, 11:26 am, dp...@pgadmin.org (Dave Page) wrote: > Did you add > > shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' > > to postgresql.conf and restart the server per the README? Oh my goodness. No. Thank you so much. It works fine now. I'll have to add that to my upgrading procedure... Kev
On Wed, Apr 8, 2009 at 4:35 PM, Kevin Field <kevinjamesfield@gmail.com> wrote: > On Apr 8, 11:26 am, dp...@pgadmin.org (Dave Page) wrote: >> Did you add >> >> shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' >> >> to postgresql.conf and restart the server per the README? > > Oh my goodness. No. Thank you so much. It works fine now. I'll > have to add that to my upgrading procedure... Excellent :-). FYI, I'm currently working on improving pgAdmin's ability to detect if the plugin is properly installed. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com