Naoya Anzai wrote
> Hi Dave,
>
> Thanks for your response.
>
>> Thanks for the patch! Curious how would you ever come across this ?
>
> This incident was reported by one of our customers.
> So I don't know why their application executes EMPTY_QUERY frequently...
>
> Regards,
The most obvious reason would be as a keep-alive query...I have no idea
whether that is a wise decision compared to "SELECT 1;" or something that
actually causes the server to perform work (i.e., what does the server do
when it see the empty-string as input?).
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/A-prepared-statement-ERROR-due-to-EMPTY-QUERY-is-defined-as-a-static-Instance-tp5795067p5795476.html
Sent from the PostgreSQL - jdbc mailing list archive at Nabble.com.