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 CAB7nPqR84Q82Fe=ix5kRgODt05v1iLjqrM71b83Tn2mhKK7qwA@mail.gmail.com
Whole thread Raw
In response to Re: Issue with bgworker, SPI and pgstat_report_stat  (Julien Rouhaud <julien.rouhaud@dalibo.com>)
Responses Re: Issue with bgworker, SPI and pgstat_report_stat  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On Mon, Jul 11, 2016 at 3:36 AM, Julien Rouhaud
<julien.rouhaud@dalibo.com> wrote:
> I'm not opposed, but in this case we should also provide a proper
> documentation of all the required actions to mimick normal backends.

I'd rather just add a note like "Have a look at PostgresMain if you
want to imitate a backend able to run queries!" instead of listing all
the actions doable. If low-level things are added or removed in the
future in PostgresMain, it is very likely that the documentation will
not be updated at the same time, killing its purpose at the end.
-- 
Michael



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Showing parallel status in \df+
Next
From: Michael Paquier
Date:
Subject: Re: Fix Error Message for allocate_recordbuf() Failure