Maciek Sakrejda <msakrejda@truviso.com> writes:
>> But to the last part of cited protocol specification, when I've sent message with statement parameter's type int4,
int8,varchar the format
>> field wasn't set to 0, but 1.
> I wasn't able to reproduce that with my standalone test case. When I
> changed the parameter oid to 23, I still got the same behavior. Can
> you alter my test case to reproduce the error?
I'd be really surprised if that affected the server-side behavior.
OTOH, it seems possible that the JDBC driver might behave differently
depending on whether parameter types were prespecified or not --- it
might issue Describe earlier in order to get the parameter types,
perhaps.
regards, tom lane
