If you use as much Perl and PostgreSQL as we do at OmniTI, you’re bound to start building complex software solutions using [http://www.postgresql.org/docs/current/interactive/plperl.html plperl]. One of our latest projects (internally known as abyss) involves long term storage and archiving of email inside of PostgreSQL. That part isn’t interesting. The interesting part is how we make use of a bunch of custom perl modules we wrote, inside of plperl, to parse, digest, and dissect the information inside of those emails, transforming the data into something that can be analyzed more thoroughly by normal database tools; essentially giving structure to the semi-structured data inside of email. One of the parts that makes plperl so handy is it’s ability to use shared variables, to pass data from one function to another inside of a backend session. Using this technique, you can really start to do some interesting things, but it does present one problem when your trying to debug, specifically how to see the values that are getting passed around in a session. Luckily the solution is a lot simpler than you would think.As you can see, we use the perl "[http://search.cpan.org/~ilyam/Data-Dumper-2.121/Dumper.pm Dumper]" module to dump out all of the shared variables you might be looking at, in a fairly oragnized manner. Woohoo! Incidentally, we're hiring Perl developers to work on things like this, as well as some other big projects using Perl and PostgreSQL, among other stuff, so if you think you have what it takes, check out our [http://www.omniti.com/people/jobs#webdev job posting] and send in that resume!