On 28/09/2016 18:46, Robert Haas wrote:
>
> Everybody seems happy with this fix for a first step, so I've
> committed it and back-patched it to 9.3.
>
Thanks!
--
Julien Rouhaud
http://dalibo.com - http://dalibo.org
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To mak
On Sat, Sep 3, 2016 at 12:29 AM, Michael Paquier
wrote:
> On Sat, Sep 3, 2016 at 10:02 AM, Tomas Vondra
> 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 w
On Sat, Sep 3, 2016 at 10:02 AM, Tomas Vondra
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 documenta
On 07/11/2016 06:53 AM, Craig Ringer wrote:
On 11 July 2016 at 11:49, Michael Paquier mailto:michael.paqu...@gmail.com>> wrote:
On Mon, Jul 11, 2016 at 3:36 AM, Julien Rouhaud
mailto:julien.rouh...@dalibo.com>> wrote:
> I'm not opposed, but in this case we should also provide a prope
On 11 July 2016 at 11:49, Michael Paquier wrote:
> On Mon, Jul 11, 2016 at 3:36 AM, Julien Rouhaud
> 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 l
On Mon, Jul 11, 2016 at 3:36 AM, Julien Rouhaud
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 r
On 08/07/2016 01:53, Michael Paquier wrote:
> On Fri, Jul 8, 2016 at 3:06 AM, Andres Freund wrote:
>> On 2016-07-07 14:04:36 -0400, Robert Haas wrote:
>>> On Thu, Jul 7, 2016 at 1:52 PM, Julien Rouhaud
>>> wrote:
Should a bgworker modifing data have to call pgstat_report_stat() to
avoid
On Fri, Jul 8, 2016 at 3:06 AM, Andres Freund wrote:
> On 2016-07-07 14:04:36 -0400, Robert Haas wrote:
>> On Thu, Jul 7, 2016 at 1:52 PM, Julien Rouhaud
>> wrote:
>> > Should a bgworker modifing data have to call pgstat_report_stat() to
>> > avoid this problem? I don't find any documentation sug
On 2016-07-07 14:04:36 -0400, Robert Haas wrote:
> On Thu, Jul 7, 2016 at 1:52 PM, Julien Rouhaud
> wrote:
> > Should a bgworker modifing data have to call pgstat_report_stat() to
> > avoid this problem? I don't find any documentation suggesting it, and it
> > seems that worker_spi (used as a temp
On Thu, Jul 7, 2016 at 1:52 PM, Julien Rouhaud
wrote:
> While investigating on a bloat issue with a colleague, we found that if
> a bgworker executes some queries with SPI, the statistic changes will
> never be reported, since pgstat_report_stat() is only called in regular
> backends.
>
> In our c
Hello,
While investigating on a bloat issue with a colleague, we found that if
a bgworker executes some queries with SPI, the statistic changes will
never be reported, since pgstat_report_stat() is only called in regular
backends.
In our case, the bgworker is the only process inserting and deleti
11 matches
Mail list logo
