I've also been able to verify that Execute() will send to destinations
different from Bind(), and that's when I get invalid portal name
errors from the backend. I think this is happening at both levels,
Bind& Execute.
Hmm. Question is why you get invalid portal name errors in the first
place.
According to http://www.postgresql.org/docs/8.3/static/protocol-flow.html
"The Describe message (portal variant) specifies the name of an existing
portal (or an empty string for the unnamed portal). The response is a
RowDescription message describing the rows that will be returned by
executing the portal; or a NoData message if the portal does not contain
a query that will return rows; or ErrorResponse if there is no such portal."
Describe messages were also being sent to the wrong node.
Regards,
-Bryan
_______________________________________________
Pgpool-general mailing list
[email protected]
http://pgfoundry.org/mailman/listinfo/pgpool-general
