Re: The logic behind the prepared statement in PostgreSQL

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: louis <louis(at)ibms(dot)sinica(dot)edu(dot)tw>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: The logic behind the prepared statement in PostgreSQL
Date: 2010-10-06 21:16:06
Message-ID: 4CACE716.5010600@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

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

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message louis 2010-10-07 05:55:04 Re: The logic behind the prepared statement in PostgreSQL
Previous Message louis 2010-10-06 13:29:42 Re: The logic behind the prepared statement in PostgreSQL