From: | Ian Campbell <ianrc72(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Unstable C Function |
Date: | 2016-09-22 16:22:07 |
Message-ID: | CA+0FpjXpZ6UGkSr=t6DYCBG9-vUcWjJJhRsMHiYr2O=h+8L1=w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm going to rewrite it to use your tuplestore suggestion.
OK, so SPI is only suitable for single-call functions, right? If another
function in the query attempted to use SPI, I assume there would be a
deadlock?
Regards, Ian
On Thu, Sep 22, 2016 at 7:25 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Ian Campbell <ianrc72(at)gmail(dot)com> writes:
> > Thanks for personally replying, Tom. I appreciate it.
> > You are correct. In the interim, I found the following change solved the
> > issue:
>
> > SPI_finish(); // move to here
> > SRF_RETURN_DONE(funcctx);
>
> That might work under light usage, but the problem with it is you're
> blocking any other function in the same query from using SPI, since
> you're leaving your own connection active when returning. Sooner
> or later that's gonna be a problem.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-09-22 16:41:21 | Re: Unstable C Function |
Previous Message | Sylvain Marechal | 2016-09-22 15:42:51 | Re: Monitor pg_xlog size via SQL with postgres 9.4 |