| From: | "Rod Taylor" <rod(dot)taylor(at)inquent(dot)com> |
|---|---|
| To: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | SPI_finish() |
| Date: | 2001-02-16 19:01:07 |
| Message-ID: | 007701c0984a$d15e8b90$2205010a@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Sorry for the lack of description, but here goes.
I have a function which runs properly, causes no errors until I call
SPI_Finish(). Upon that call the backend closes (not what I want).
If I remove that line (leaving in the SPI_Connect() statement) it runs
fine, but issues numerous warnings about connections already having
been established.
Is there a known way to make SPI_Finish() crash that I could have run
into? Function consists of a couple selects and a couple inserts.
Of course, removing both SPI_Connect() doesn't allow the queries to be
performed.
--
Rod Taylor
There are always four sides to every story: your side, their side, the
truth, and what really happened.
| Attachment | Content-Type | Size |
|---|---|---|
| Taylor, Rod B.vcf | text/x-vcard | 451 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2001-02-16 19:02:49 | Re: order of clauses |
| Previous Message | Michael Fork | 2001-02-16 18:59:20 | Re: order of clauses |