Re: broken documentation: BackgroundWorkerInitializeConnection(NULL, NULL);

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: broken documentation: BackgroundWorkerInitializeConnection(NULL, NULL);
Date: 2015-05-15 20:14:10
Message-ID: CA+Tgmob6Q2XcMGMVwMgoF6EDhjuuakFKk6kqYuKfd6upBu89_A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 15, 2015 at 4:07 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Robert Haas wrote:
>> On Fri, May 15, 2015 at 3:53 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
>> > The test code I used to verify that this works is also attached.
>> >
>> > If there are no objections, I will commit and back-patch.
>>
>> Oops. Really attached this time.
>
> We have spi_worker in src/test/modules now -- I think it makes sense to
> add this one there too in master.

Really? I was thinking of the test code as throwaway. I just wanted
to fix the bug.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-05-15 20:15:37 Re: log bloating with shortlife bgworkers?
Previous Message Robert Haas 2015-05-15 20:13:10 Re: trust authentication behavior