From: | Chris Ernst <cernst(at)esoft(dot)com> |
---|---|
To: | Dimitri Fontaine <dfontaine(at)hi-media(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-21 14:24:39 |
Message-ID: | 4B2F8527.1030402@esoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dimitri Fontaine wrote:
> 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.
Ouch! You're right. And that's would be a deal killer for me. About
90% of the traffic is prepared queries that are run over and over with
different parameters.
- Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2009-12-21 15:23:18 | Re: Selecting from table into an array var |
Previous Message | Durumdara | 2009-12-21 14:24:19 | Re: Charset Win1250 on Windows and Ubuntu |