From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Oliver Jowett <oliver(at)opencloud(dot)com>, 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 |
Subject: | Re: prepareThreshold=1 and statement.executeBatch() ?? |
Date: | 2005-11-16 00:47:34 |
Message-ID: | 200511160047.jAG0lY315592@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
Tom Lane wrote:
> 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.
The output does look slightly different and was approved by the folks
using this feature. I don't understand the panic about it.
If people using the feature want to submit a patch to modify it, that
seems fine.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Glaesemann | 2005-11-16 00:56:13 | Re: Long-time 7.4 contrib failure Mac OS X 10.3.8 |
Previous Message | Yann Michel | 2005-11-16 00:34:32 | Re: PG_DUMP and table locking in PG7.4 |
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2005-11-16 16:34:13 | Re: Problem with storing Images in PostgreSQL |
Previous Message | Kris Jurka | 2005-11-14 05:41:11 | Re: ErrorCodes suddenly stopped working? [possibly my |