Re: PGStatement#setPrepareThreshold - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: PGStatement#setPrepareThreshold
Date
Msg-id 14825.1154718943@sss.pgh.pa.us
Whole thread Raw
In response to Re: PGStatement#setPrepareThreshold  (Bruce Momjian <bruce@momjian.us>)
List pgsql-jdbc
Bruce Momjian <bruce@momjian.us> writes:
> Did you like my idea of?
>     statement:  <protocol execute> ...

No.

> I want to keep the "statement:" prefix for scripts
> that process our log files, and because it is output by log_statement,
> which controls protocol output as well.

I think that's an irrelevant consideration, but it's driving you
to insist on unnecessarily complicated, confusing output.  What's
wrong with "parse:", "bind:", and "execute:"?  If you really must
have the word "statement" in there, then let's do "parse statement:"
"bind statement:" and "execute statement:".  In any case we've got
to drop all the brackets and braces, they look too much like they might
be part of the statement string.

            regards, tom lane

pgsql-jdbc by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: PGStatement#setPrepareThreshold
Next
From: Dave Cramer
Date:
Subject: Re: PGStatement#setPrepareThreshold