Date: Fri, 30 May 2014 20:13:24 -0700 (PDT)
From: David G Johnston <david.g.johnston@gmail.com>
To: pgsql-interfaces@postgresql.org
Message-ID: <1401506004684-5805644.post@n5.nabble.com>
In-Reply-To: <13879676.rjCYEBPBaJ@amber>
References: <1422083.cnnU3SmOMV@amber> <9955.1401483874@sss.pgh.pa.us>
 <13879676.rjCYEBPBaJ@amber>
Subject: Re: Console output with libpq
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-interfaces-owner@postgresql.org

alpha_one_x86 wrote
> Hello,
> 
>> You're barking up the wrong tree
> I don't understand. Wrong mailling list?

Yes, English phrases can be so fun.

This particular one means that the approach or area of your search is not
one that is causing the problem or likely to yield a solution. 
Specifically, those PQset... functions are not the source of your problem
nor usable for solving it.  More broadly it isn't even a libpq problem at
all.

Imagine two trees with a cat in one of them.  Now imagine a dog barking at
the tree the cat isn't in.  That dog is barking up the wrong tree if it is
attempting to bark at the cat.

David J.


--
View this message in context: http://postgresql.1045698.n5.nabble.com/Console-output-with-libpq-tp5805610p5805644.html
Sent from the PostgreSQL - interfaces mailing list archive at Nabble.com.


-- 
Sent via pgsql-interfaces mailing list (pgsql-interfaces@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-interfaces