Thread: pldebugger server-side plugin
Hi, The PL/pgSQL debugger included in pgadmin needs a bunch of server-side support functions to be installed in the server. The code for the server-side functions is currently located in a pgfoundry CVS repository, in the edb-debugger project. It's time to give that code facelift. I have converted the CVS repository to git using git-cvsimport, now available at git://git.postgresql.org/git/pldebugger.git. After that, I did a lot of cleanup and refactoring. The functionality should be unchanged, and it should still work against older server versions. The CVS repository also contained a plugin_profiler thingie, that was not related to plugin_debugger. I removed that. It might be a useful project, but I don't think anyone has really looked at it for years, and it really ought to be a separate project and repository, since it doesn't have anything to do with the debugger plugin. If someone wants to resurrect that code, it can be dug from the history of the git repository. There's still plenty of cleanup that could be done to the plugin, but this is a good start. The plugin doesn't have a mailing list of its own, and AFAIK pgadmin is the only consumer of that API, so let's keep pldebugger related discussions on this mailing list. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
Thanks Heikki. On Mon, Apr 16, 2012 at 3:58 PM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: > Hi, > > The PL/pgSQL debugger included in pgadmin needs a bunch of server-side > support functions to be installed in the server. The code for the > server-side functions is currently located in a pgfoundry CVS repository, in > the edb-debugger project. > > It's time to give that code facelift. I have converted the CVS repository to > git using git-cvsimport, now available at > git://git.postgresql.org/git/pldebugger.git. After that, I did a lot of > cleanup and refactoring. The functionality should be unchanged, and it > should still work against older server versions. > > The CVS repository also contained a plugin_profiler thingie, that was not > related to plugin_debugger. I removed that. It might be a useful project, > but I don't think anyone has really looked at it for years, and it really > ought to be a separate project and repository, since it doesn't have > anything to do with the debugger plugin. If someone wants to resurrect that > code, it can be dug from the history of the git repository. > > There's still plenty of cleanup that could be done to the plugin, but this > is a good start. > > The plugin doesn't have a mailing list of its own, and AFAIK pgadmin is the > only consumer of that API, so let's keep pldebugger related discussions on > this mailing list. > > -- > Heikki Linnakangas > EnterpriseDB http://www.enterprisedb.com > > -- > Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-hackers -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
On Mon, 2012-04-16 at 18:58 +0300, Heikki Linnakangas wrote: > Hi, > > The PL/pgSQL debugger included in pgadmin needs a bunch of server-side > support functions to be installed in the server. The code for the > server-side functions is currently located in a pgfoundry CVS > repository, in the edb-debugger project. > > It's time to give that code facelift. I have converted the CVS > repository to git using git-cvsimport, now available at > git://git.postgresql.org/git/pldebugger.git. After that, I did a lot of > cleanup and refactoring. The functionality should be unchanged, and it > should still work against older server versions. > > The CVS repository also contained a plugin_profiler thingie, that was > not related to plugin_debugger. I removed that. It might be a useful > project, but I don't think anyone has really looked at it for years, and > it really ought to be a separate project and repository, since it > doesn't have anything to do with the debugger plugin. If someone wants > to resurrect that code, it can be dug from the history of the git > repository. > > There's still plenty of cleanup that could be done to the plugin, but > this is a good start. > > The plugin doesn't have a mailing list of its own, and AFAIK pgadmin is > the only consumer of that API, so let's keep pldebugger related > discussions on this mailing list. > That's really great. Thank you, Heikki. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com