On Tue, Feb 7, 2017 at 2:04 AM, Amit Kapila <amit.kapil...@gmail.com> wrote: > On Tue, Feb 7, 2017 at 10:44 AM, Mithun Cy <mithun...@enterprisedb.com> wrote: >> >> ================== >> One problem now I have kept it open is multiple "auto pg_prewarm dump" >> can be launched even if already a dump/load worker is running by >> calling launch_pg_prewarm_dump. I can avoid this by dropping a >> lock-file before starting the bgworkers. But, if there is an another >> method to avoid launching bgworker on a simple method I can do same. >> > > How about keeping a variable in PROC_HDR structure to indicate if > already one dump worker is running, then don't allow to start a new > one?
A contrib module shouldn't change core (and shouldn't need to). It can register its own shared memory area if it wants. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
