Re: Problem with background worker - Mailing list pgsql-hackers

From Guillaume Lelarge
Subject Re: Problem with background worker
Date
Msg-id 1364122809.4019.2.camel@localhost.localdomain
Whole thread Raw
In response to Re: Problem with background worker  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Wed, 2013-03-20 at 13:13 -0300, Alvaro Herrera wrote:
> Marc Cousin escribió:
> > On 20/03/2013 16:33, Alvaro Herrera wrote:
>
> > >Ah.  The reason for this problem is that the statement start time (which
> > >also sets the transaction start time, when it's the first statement) is
> > >set by postgres.c, not the transaction-control functions in xact.c.  So
> > >you'd need to add a SetCurrentStatementStartTimestamp() call somewhere
> > >in your loop.
> >
> > Yes, that works. Thanks a lot !
> >
> > Maybe this should be added to the worker_spi example ?
>
> Yeah, I think I need to go over the postgres.c code and figure out what
> else needs to be called.  I have a pending patch from Guillaume to
> improve worker_spi some more; I'll add this bit too.
>

Happy to know that you still remember it :) Thanks.


--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com




pgsql-hackers by date:

Previous
From: Hitoshi Harada
Date:
Subject: Re: Request for Patch Feedback: Lag & Lead Window Functions Can Ignore Nulls
Next
From: Simon Riggs
Date:
Subject: Limiting setting of hint bits by read-only queries; vacuum_delay