On Thu, Aug 4, 2011 at 16:34, David E. Wheeler <da...@kineticode.com> wrote: > On Aug 4, 2011, at 3:09 PM, Alex Hunsaker wrote: > >> Mainly the options im thinking about are: >> 1) if anyone touches %SIG die >> 2) turn %SIG into a regular hash so people can set/play with %SIG, but >> it has no real effect. > > These would disable stuff like $SIG{__WARN__} and $SIG{__DIE__}, which would > be an unfortunate side-effect.
Yeah, good point. >> 3) local %SIG before we call their trigger function. This lets signals >> still work while "in trigger scope" (like we do for %_TD) > > +1 That seems to be what most people up-thread thought as well. I dont see it being too expensive. Ill see if I can whip something up today. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers