Libpq problems

From: Dirk Elmendorf <delmendo(at)cymitar(dot)net>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: Libpq problems
Date: 1998-08-13 15:57:39
Message-ID: XFMail.980813105739.delmendo@cymitar.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

I have a program which opens two connections to two different databases.
After issuing a few commands to the second database I this get in the trace log:

To backend> QSELECT oid FROM order_table WHERE customer_number=936 ;
>From backend> N
>From backend> "NOTICE: SIMarkEntryData: cache state reset

Then I get a SIGPIPE on the first database which courrpts my connection. The
funny thing i
s that PQstatus still says I have a good connection.The second database
continues plugging
along. I cannot seem to figure out how to stop this - if I re-issuse all the
SQL in psql
each command works like a charm - but when I do it through libpq I can not
seem to escape
the problem - Has anyone else run into this problem? Can anyone explain what
this Notice
means? I searched through the Mailing lists and found a number of emails asking the same
quesiton- but no answer could be found. Any insight would be greatly appreciated.
I'm running 6.3.2 on RH 4.2

I tried opening the first db grabbing some info and then closing the connection- then I op
en the second databse- I'm still able to generate this error.
_________________________________________________________
Dirk Elmendorf, VP/Development Main: 210-892-4000
Cymitar Technology Group, Inc. Direct: 210-892-4005
Lorene Office Plaza Fax: 210-892-4329
9828 Lorene Lane <http://www.cymitar.com>
San Antonio, TX 78216-4450 <delmendo(at)cymitar(dot)com>
_________________________________________________________

Browse pgsql-interfaces by date

  From Date Subject
Next Message Tom Lane 1998-08-13 16:08:18 Re: [INTERFACES] '\' and varchar data type problem w/ MS Access a nd ODBC driver
Previous Message Tom Lane 1998-08-13 15:14:45 Re: [INTERFACES] '\' and varchar data type problem w/ MS Access a nd ODBC driver