Re: Injection point locking - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Injection point locking
Date
Msg-id 971878.1720448269@sss.pgh.pa.us
Whole thread Raw
In response to Re: Injection point locking  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: Injection point locking
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: "feichanghong"
Date:
Subject: Re: Optimize commit performance with a large number of 'on commit delete rows' temp tables
Next
From: Nathan Bossart
Date:
Subject: Re: 回复:Re: 回复:Re: speed up pg_upgrade with large number of tables