| From: | louis <louis(at)ibms(dot)sinica(dot)edu(dot)tw> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: The logic behind the prepared statement in PostgreSQL |
| Date: | 2010-10-07 05:55:04 |
| Message-ID: | 1286430904.7465.4.camel@london |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Thu, 2010-10-07 at 10:16 +1300, Oliver Jowett wrote:
> louis wrote:
>
> > However, while tracing the call stack I found that the
> > core.v3.QueryExecutorImpl.sendBind method sends a query statement Name
> > to PGStream, does it mean JDBC driver use the statement name to identify
> > the corresponding execution plan on a Postgresql server?
> > I have such assumption since PGStream seems to be the connection between
> > JDBC driver and the PostgreSQL server, and I can't find other obvious
> > path for JDBC code to specify an execution plan on the server side.
>
> A Bind message associates parameter values with a previously created
> statement. You probably want to read the docs that describe the FE/BE
> protocol: http://www.postgresql.org/docs/9.0/static/protocol.html
>
> Oliver
>
Very helpful information.
Much appreciated
Louis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | guanyi | 2010-10-07 07:30:28 | jdbc pool problem |
| Previous Message | Oliver Jowett | 2010-10-06 21:16:06 | Re: The logic behind the prepared statement in PostgreSQL |