Re: Issue with bgworker, SPI and pgstat_report_stat - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Issue with bgworker, SPI and pgstat_report_stat
Date
Msg-id CAB7nPqQN6grBMmK9tK5AjV++LcCKsZnwB-MHBXCajU-Ps==TEA@mail.gmail.com
Whole thread Raw
In response to Re: Issue with bgworker, SPI and pgstat_report_stat  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: Issue with bgworker, SPI and pgstat_report_stat  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Sat, Sep 3, 2016 at 10:02 AM, Tomas Vondra
<tomas.vondra@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Claudio Freire
Date:
Subject: Vacuum: allow usage of more than 1GB of work mem
Next
From: Tom Lane
Date:
Subject: Re: standalone backend PANICs during recovery