| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | Joost Kraaijeveld <J(dot)Kraaijeveld(at)Askesis(dot)nl>, Kris Jurka <books(at)ejurka(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Subject: | Re: prepareThreshold=1 and statement.executeBatch() ?? |
| Date: | 2005-11-13 16:04:55 |
| Message-ID: | 4403.1131897895@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
Oliver Jowett <oliver(at)opencloud(dot)com> writes:
> The driver does not actually issue PREPARE or EXECUTE statements; the
> server is pretending that the protocol-level Prepare/Bind/Execute
> messages are actually something issuing PREPARE/EXECUTE at the SQL level
I had not realized that the logging code recently added to Parse/Bind/Execute
deliberately obscures the difference between a Parse message and an SQL
PREPARE (etc). This is a terrible decision IMHO and needs to be fixed
forthwith.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-11-13 16:12:19 | Re: Multi-table-unique-constraint |
| Previous Message | Tom Lane | 2005-11-13 15:28:28 | Re: Multi-table-unique-constraint |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2005-11-13 19:02:22 | Re: prepareThreshold=1 and statement.executeBatch() ?? |
| Previous Message | Oliver Jowett | 2005-11-13 10:09:24 | Re: prepareThreshold=1 and statement.executeBatch() ?? |