Is there any way to set transaction isolation level inside plpgsql function?
In my case I have no control of transaction before function is started.
--
Sincerely,
Sergey Moroz
this case on simple query
like 'select field1 from table1 limit 100'.
--
Sincerely,
Sergey Moroz
this idea cause any problems?
--
Sincerely,
Sergey Moroz
I think the same way :). But as I mentioned in the first letter I'm not a C
guy. So I wonder why doesn't postgres store hashes for all queries and
misses parsing step if not needed like Oracle does?
On 8/3/07, Sibte Abbas <[EMAIL PROTECTED]> wrote:
>
> On 8/3/07, Sergey M
returned result as SETOF. In case of such a query had been
executed at least once, prepare step should be excluded (stored execution
plan should be used).
On 8/3/07, Sibte Abbas <[EMAIL PROTECTED]> wrote:
>
> On 8/2/07, Sergey Moroz <[EMAIL PROTECTED]> wrote:
> > The problem
The problem is that I can't find the way to exclude query parsing (prepare
step) for custom queries. In other words I want to create a function that
accepts a query text with "$1, $2, etc." and variables as params, executes
the query and returns a set of record. I could use 'execute' in plpgsql but
