From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David McClellan and Alun Prytherch" <David(dot)McClellan(at)ateb(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #1600: Interrupt routine causes libPQ call to fail w/o error |
Date: | 2005-04-17 00:50:10 |
Message-ID: | 26570.1113699010@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"David McClellan and Alun Prytherch" <David(dot)McClellan(at)ateb(dot)com> writes:
> We are using a Postgres database on Linux to service both a webapp and a
> backend process. The backend process is written in GCC-compile standard C,
> and uses libpq to query, insert and update records in the database. It is a
> pharmacy-service app, and also interfaces with DialLogic cards to make phone
> calls. The DialLogic cards support event-callback routines and will
> interrupt the background process with callbacks, even during the process's
> database calls.
Perhaps one of your interrupt routines tried to do something with the
database connection? That certainly won't work safely.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Trawick | 2005-04-17 02:29:04 | BUG #1604: Composite types, triggers, and INET_CLIENT_ADDR() function |
Previous Message | Jaime Casanova | 2005-04-16 23:18:19 | Re: BUG #1601: removing columns |