Re: spi in bgworker - Mailing list pgsql-general

From James Harper
Subject Re: spi in bgworker
Date
Msg-id F214C06498BC244DB3F9472E1C5368180F41E488@BITCOM1.int.sbss.com.au
Whole thread Raw
In response to Re: spi in bgworker  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-general
>
> James Harper wrote:
> > The docs say I'm supposed to call BackgroundWorkerInitializeConnection in
> a bgworker and then I can start using spi functions, but they aren't clear on if
> I should call SPI_connect too.
> >
> > If I call BackgroundWorkerInitializeConnection and then SPI_execute I get a
> return code of SPI_ERROR_UNCONNECTED. If I call
> BackgroundWorkerInitializeConnection then SPI_connect I get a segfault.
>
> You need to start a transaction after initializing the database
> connection.  Did you see the sample worker_spi code in contrib?
>

I have now. Thanks!

Is the documentation here a bit light because background workers are a new feature? Or is this general postgres
knowledgeI just haven't picked up on yet? 

Could SPI_connect return an error rather than crashing?

Thanks again

James


pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: spi in bgworker
Next
From: Andreas Joseph Krogh
Date:
Subject: Default operator class for data type boolean for access method gist is missing