Re: EXECUTE problems

From: Neil Conway <neilc(at)samurai(dot)com>
To: Medi Montaseri <medi(dot)montaseri(at)intransa(dot)com>
Cc: Felipe Schnack <felipes(at)ritterdosreis(dot)br>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: EXECUTE problems
Date: 2002-11-26 19:12:03
Message-ID: 877kf0m9h8.fsf@mailbox.samurai.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Medi Montaseri <medi(dot)montaseri(at)intransa(dot)com> writes:
> Before I head out to read those links....do I have to re-prepare if
> I loose my connection. Or could/would the backend use it regardless
> of what connection I come in....

No, prepared statements are currently stored locally, per-backend --
that means that a prepared statement can only be EXECUTE'd by the same
client that PREPARE'd it. We looked into storing prepared queries in
shared memory (in fact, the first implementations of the idea did just
that), but it turned out not to be worth the hassle.

> Also I need some help using Async query technique....anyone used who
> I can get some help from....I need to confirm my understanding of
> how to use the Async Query technique

Do you have a specific question that isn't addressed by the
documentation?

http://developer.postgresql.org/docs/postgres/libpq-async.html

Cheers,

Neil

--
Neil Conway <neilc(at)samurai(dot)com> || PGP Key ID: DB3C29FC

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bjoern Metzdorf 2002-11-26 19:41:45 Re: Updating table with max from another table
Previous Message Bruce Momjian 2002-11-26 19:10:49 Re: eXtreme PostgreSQL using system catalogs (was Turning