Re: C vs plpgsql and child processes - Mailing list pgsql-general

From Sean Chittenden
Subject Re: C vs plpgsql and child processes
Date
Msg-id 20030817184810.GB88411@perrin.int.nxad.com
Whole thread Raw
In response to C vs plpgsql and child processes  (Jason Godden <jasongodden@optushome.com.au>)
Responses Re: C vs plpgsql and child processes  (Jason Godden <jasongodden@optushome.com.au>)
List pgsql-general
> Problem is that when I call these particular functions from within
> plpgsql rather than through a single sql command the child never
> actually starts (or starts and then exits immediately).

Are you sure?  I can't think of much that'd prevent a C function from
executing other than how you've declared the function (ie, is PgSQL
caching the results of the function?).  Make sure you've declared it
as VOLATILE (or don't declare it anything and it'll default to
VOLATILE).

http://developer.postgresql.org/docs/postgres/sql-createfunction.html

-sc

--
Sean Chittenden

pgsql-general by date:

Previous
From: Karsten Hilbert
Date:
Subject: Re: Need feedback on new feature (\for)
Next
From: "James Moe"
Date:
Subject: Too many clients