Looks like other people were asking similar question, but there is no answer: http://forums.devshed.com/postgresql-help-21/combine-prepare-and-declare-cursor-437562.html
On Mon, Jun 28, 2010 at 1:00 AM, Konstantin Izmailov <pgfizm@xxxxxxxxx> wrote:
lolSeriosly, this customer issues resulted in improvement of the way our driver prepares statements. Keeping the map of prepared statements names is actually faster than using Savepoints (less roundtrips to server).
I found that DECLARE ... CURSOR FOR ... cannot be prepared. Basically I'm looking for a way to prepare a complex query and then use cursor for reading tuples. Is this possible?This works: PREPARE abcd AS SELECT * FROM test; EXECUTE abcd;This does not work: PREPARE sdsdsd AS DECLARE csr1 CURSOR FOR SELECT * FROM test;This does not work (after prepared the query): DECLARE csr1 CURSOR FOR EXECUTE abcd;Thank you!
KonstantinOn Wed, Jun 23, 2010 at 9:41 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
Scott Marlowe <scott.marlowe@xxxxxxxxx> writes:
> On Wed, Jun 23, 2010 at 10:55 PM, Konstantin Izmailov <pgfizm@xxxxxxxxx> wrote:
>> The company is not willing to upgrade from 7.4 to a later version due to
>> risk.> The risk of upgrading is less than the risk of staying on anIndeed. Point out to them that 7.4 is going to be unsupported after the
> unsupported version of pgsql. The company that won't upgrade is
> making a poorly informed decision.
end of this month:
http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy
If they don't have a plan to get off of 7.4 within the pretty near
future, they're fools.
regards, tom lane