On Wed, Aug 24, 2011 at 1:16 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > I agree you probably don't want to poke at this in your production > instance, but you could create a playpen instance (separate data > directory, nondefault port number) using the same executables and > then do your testing there. If you didn't want to get plperl going > on that machine, why'd you try it in the first place? Good idea about using a separate data dir etc, I'll try that out. As far as not wanting plperl in the first place, I didn't mean to imply that. I've used plperl(u) functions before (but not since 8.4), so it was never an issue on this particular production machine before. I've had no problems in the other dev and test databases where I've found uses for plperl functions -- none are currently lower than 9.0.4 however. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
