| From: | James Harper <james(dot)harper(at)bendigoit(dot)com(dot)au> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: spi in bgworker |
| Date: | 2014-03-22 23:54:45 |
| Message-ID: | F214C06498BC244DB3F9472E1C5368180F41E488@BITCOM1.int.sbss.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 knowledge I just haven't picked up on yet?
Could SPI_connect return an error rather than crashing?
Thanks again
James
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2014-03-23 00:20:28 | Default operator class for data type boolean for access method gist is missing |
| Previous Message | Alvaro Herrera | 2014-03-22 23:49:28 | Re: spi in bgworker |