Alan Nilsson <anilsson@apple.com> writes:
> What I am saying is that something changed in 90300 that causes libpq to spew to stdout where it had not in libpq
90102& 90203.
Well, that's interesting, but the issue is not in libpq, and you've still
provided no information that would help anyone diagnose where it is
(like, say, the query that's producing different results).
> I guess i am blaming the messenger because there should be no messenger. Regardless of how badly I mangle the use of
libpq,it should not be sending anything to stdout.
Would you prefer it dumped core? It doesn't have very many choices for
reporting that you've passed invalid arguments. In any case, the short
answer is that if you'd like this code fragment to do X when the query
has returned zero rows, you should explicitly code a test for that.
Otherwise you're at the mercy of somebody else's idea of what to do
with the error condition.
Also, if your gripe is not so much that it resorted to printing a message
as exactly how it printed it, see libpq's options for inserting your own
message processing hooks.
regards, tom lane
