plpgsql and prep statements (performance and sql injection) - Mailing list pgsql-general

From Wim Bertels
Subject plpgsql and prep statements (performance and sql injection)
Date
Msg-id 1309943497.2333.43.camel@zwerfkat
Whole thread Raw
Responses Re: plpgsql and prep statements (performance and sql injection)
List pgsql-general
Hallo,

good reasons to use prep statements
seem
- performance
- some sql injection defence

but when i look at plpgsql
http://www.postgresql.org/docs/8.4/interactive/plpgsql-implementation.html
i see that sql statements are translated into prep statements,
and live (the plan) as long the db connection is open

so there seems nothing to be gained from using
prep statements inside a plpgsql function,
the only reason could be the lifecycle of the prep statements
(which u don't really control for the translated sql functions inside
plpgsql functions). So i would be nice to have an extra feature in
plpgsql functions like imm,sta,vol (planning) but then to control the
duration/lifetime of the translated statements inside the plpgsql
function.

also,
since the keyword 'EXECUTE' is ambivalent i don't see at this point how
u can execute a prep statement inside a plpgsql function.

Comments?

mvg,
Wim






pgsql-general by date:

Previous
From: Durumdara
Date:
Subject: Re: When the Session ends in PGSQL?
Next
From: Pavel Stehule
Date:
Subject: Re: plpgsql and prep statements (performance and sql injection)