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

From Alvaro Herrera
Subject Re: Problem with background worker
Date
Msg-id 20130320161322.GB3688@alvh.no-ip.org
Whole thread Raw
In response to Re: Problem with background worker  (Marc Cousin <cousinmarc@gmail.com>)
Responses Re: Problem with background worker  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgsql-hackers
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.

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Marc Cousin
Date:
Subject: Re: Problem with background worker
Next
From: Tom Lane
Date:
Subject: Re: pg_upgrade segfaults when given an invalid PGSERVICE value