| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Marc Cousin <marc(dot)cousin(at)dalibo(dot)com> |
| Subject: | Re: Issue with bgworker, SPI and pgstat_report_stat |
| Date: | 2016-09-03 04:29:32 |
| Message-ID: | CAB7nPqQN6grBMmK9tK5AjV++LcCKsZnwB-MHBXCajU-Ps==TEA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Sep 3, 2016 at 10:02 AM, Tomas Vondra
<tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> In any case, I think adding the pgstat_report_stat() into worker_spi seems
> like a reasonable (and backpatchable) fix.
Doing just that sounds reasonable seen from here. I am wondering also
if it would not be worth mentioning in the documentation of the
bgworkers that users trying to emulate somewhat the behavior of a
backend should look at PostgresMain(). The code in itself is full of
hints as well.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-09-03 06:05:00 | Re: standalone backend PANICs during recovery |
| Previous Message | Claudio Freire | 2016-09-03 03:25:37 | Vacuum: allow usage of more than 1GB of work mem |