Re: Injection point locking

Heikki Linnakangas <hlinnaka@iki.fi> writes:
> Note that until we actually add an injection point to a function that 
> runs in the postmaster, there's no risk. If we're uneasy about that, we 
> could add an assertion to InjectionPointRun() to prevent it from running 
> in the postmaster, so that we don't cross that line inadvertently.

As long as we consider injection points to be a debug/test feature
only, I think it's a net positive that one can be set in the
postmaster.  I'd be considerably more uncomfortable if somebody
wanted to do that in production, but maybe it'd be fine even then.

            regards, tom lane