From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Status of plperl inter-sp calling |
Date: | 2010-01-06 15:56:01 |
Message-ID: | 2732.1262793361@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I don't understand that phrase "call SPI with the right arguments for
> the type of function you're currently in". What calls that we make from
> plperl code would have different arguments depending on the volatility
> of the function?
eg, in plperl_spi_exec,
spi_rv = SPI_execute(query, current_call_data->prodesc->fn_readonly,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
limit);
> If a cached plan is going to behave differently, I'd be
> inclined to say that we should only allow direct inter-sp calling to
> volatile functions from volatile functions - if U understand you right
> the only problem could be caused by calling in this direction, a
> volatile function calling a stable function would not cause a problem.
The other way is just as wrong.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-01-06 16:07:04 | Re: patch - per-tablespace random_page_cost/seq_page_cost |
Previous Message | Andrew Dunstan | 2010-01-06 15:39:49 | Re: Status of plperl inter-sp calling |