>You must send either Flush or Sync after the Parse to force the backend >to emit its response to Parse. The assumption is that in many cases >you'll be sending Parse as part of a batch of commands, and the backend >should batch its responses to minimize the number of network packets >sent. So you have to tell it where the batch boundaries are --- thus, >Flush or Sync. See the docs concerning the difference between the two.
I have the same problem some days ago with the implementation of the version 3.0 protocol in C# and now using Flush it's working quite well :)
-- Best regards
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
