| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Akash Agrawal <aagrawa6(at)ncsu(dot)edu> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: How to kill a Background worker and Its metadata |
| Date: | 2016-06-27 23:59:46 |
| Message-ID: | CAB7nPqQzd0Q9eJKjL43PGBXuCc=pyh_Wy+b2fHwkf=SPycZ-6Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 28, 2016 at 3:27 AM, Akash Agrawal <aagrawa6(at)ncsu(dot)edu> wrote:
> I've created a background worker and I am using Postgresql-9.4. This
> bgworker handles the job queue dynamically and goes to sleep if there is no
> job to process within the next 1 hour.
>
> Now, I want to have a mechanism to wake the bgworker up in case if someone
> adds a new job while the bgworker is in sleep mode. So to do it, I have
> created a trigger which initially removes the existing background worker and
> then registers a new one. I am using the following two queries inside it:
Why don't you just register and use a signal in this case? You could
even do something with SIGHUP...
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Akash Agrawal | 2016-06-28 00:28:53 | Re: How to kill a Background worker and Its metadata |
| Previous Message | Robert Haas | 2016-06-27 22:05:41 | Re: Documentation fixes for pg_visibility |