From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
---|---|
To: | Chris Ernst <cernst(at)esoft(dot)com> |
Cc: | Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Extracting SQL from logs in a usable format |
Date: | 2009-12-20 19:16:08 |
Message-ID: | 6F608025-00E1-4A77-A8FF-E40078A6FC4F@hi-media.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Le 19 déc. 2009 à 16:20, Chris Ernst a écrit :
> Hmm.. That does look very interesting. The only thing that concerns me
> is where it says it supports "Basic Queries (Extended queries not yet
> supported)". I'm not sure what is meant by "Extended queries". Any idea?
I think it refers to the Extended Query support in the frontend / backend protocol, as in the documentation:
http://www.postgresql.org/docs/8.4/static/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY
The extended query protocol breaks down the above-described simple query protocol into multiple steps. The results of preparatory steps can be re-used multiple times for improved efficiency. Furthermore, additional features are available, such as the possibility of supplying data values as separate parameters instead of having to insert them directly into a query string
So that's for parse/bind/execute communications, which are used in prepare/execute and queryParam I think.
--
dim
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2009-12-20 20:10:01 | Re: Justifying a PG over MySQL approach to a project |
Previous Message | Raimon Fernandez | 2009-12-20 19:11:49 | Re: Extended Query, flush or sync ? |