Michael Van Canneyt wrote:
The program is not creating explicit transactions and only has read
access to the table. I'm establishing a connection during program
initialisation and then alternating between two query objects, it's
the activation of the query object which is causing a short-term
On Sat, 1 Jan 2011, Mark Morgan Lloyd wrote:
Michael Van Canneyt wrote:
On Fri, 31 Dec 2010, Mark Morgan Lloyd wrote:
I've just taken our name server down for maintenance, and noted that a
db-aware app I'd left running ground to a halt despite the fact that it
was only activating queries,
Michael Van Canneyt wrote:
On Fri, 31 Dec 2010, Mark Morgan Lloyd wrote:
I've just taken our name server down for maintenance, and noted that a
db-aware app I'd left running ground to a halt despite the fact that
it was only activating queries, not establishing new (named) connections.
The c
On Fri, 31 Dec 2010, Mark Morgan Lloyd wrote:
I've just taken our name server down for maintenance, and noted that a
db-aware app I'd left running ground to a halt despite the fact that it was
only activating queries, not establishing new (named) connections.
The connection was being made b
I've just taken our name server down for maintenance, and noted that a
db-aware app I'd left running ground to a halt despite the fact that it
was only activating queries, not establishing new (named) connections.
The connection was being made by host name rather than by dotted-quad
address, r
