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

From Robert Haas
Subject Re: Issue with bgworker, SPI and pgstat_report_stat
Date
Msg-id CA+TgmoY61zbqZjBiWT=jkFkf9sGacG+pjkTnv0uKZZw2t0nsYw@mail.gmail.com
Whole thread Raw
In response to Re: Issue with bgworker, SPI and pgstat_report_stat  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Issue with bgworker, SPI and pgstat_report_stat  (Julien Rouhaud <julien.rouhaud@dalibo.com>)
List pgsql-hackers
On Sat, Sep 3, 2016 at 12:29 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> 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.

Everybody seems happy with this fix for a first step, so I've
committed it and back-patched it to 9.3.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [COMMITTERS] pgsql: pg_ctl: Detect current standby state from pg_control
Next
From: Robert Haas
Date:
Subject: Re: IF (NOT) EXISTS in psql-completion