From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Palle Girgensohn <girgen(at)pingpong(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: prepared statements don't log arguments? |
Date: | 2005-04-08 07:11:25 |
Message-ID: | 10096.1112944285@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Oliver Jowett <oliver(at)opencloud(dot)com> writes:
> Simon Riggs wrote:
>> OK, thats what I hoped you'd say. With a prepared query all of the
>> statements execute the same plan, so you don't need to know the exact
>> parameters.
> This isn't true in 8.0 if you are using the unnamed statement (as the
> JDBC driver does in some cases): the plan chosen depends on the
> parameter values given in the first Bind.
Also, "what plan got chosen" isn't the only question that a DBA might
want the log to answer. "Where did my data get screwed up" is at least
as likely an application.
I'm a bit worried about the costs of converting binary-format parameters
into text form ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bernd Helmle | 2005-04-08 09:04:37 | Re: Call for objections: merge Resdom with TargetEntry |
Previous Message | Oliver Jowett | 2005-04-08 06:57:32 | Re: prepared statements don't log arguments? |