Re: Cancelled statement due to lost connection

Well, I set the timeout to 480 in the web.config. It still broke. However, I
pointed the .NET page to a different box running PostgreSQL with the same
tables and the page worked. Perhaps it's the hardware, then? The initial box
(devtest) is running Windows Server 2003 SE with SP 1. The hardware is an
AMD Athlon 64 Processor 3000+ 2.12GHz, and only 960 MB of RAM. The other box
(fudd) is running Windows Server 2003 WE SP 1. The hardware is an AMD Athlon
64 X2 Dual with the Core Processor being 3800+ 2.01 GHz, and 1 GB of RAM.

At this point I'm suspecting that devtest is running out of memory causing
the connection to be terminated. Is this a valid assumption?

The table I'm querying has 223945 rows and I'm intersecting their geometries
with a given buffer. It returns 62 rows after calculating the number of rows
within the intersection.

Thanks,
-Frances

-----Original Message-----
From: pgsql-novice-owner(at)postgresql(dot)org
[mailto:pgsql-novice-owner(at)postgresql(dot)org] On Behalf Of Brandon Aiken
Sent: Friday, September 29, 2006 1:31 PM
To: Frances Collier; pgsql-novice(at)postgresql(dot)org
Subject: Re: [NOVICE] Cancelled statement due to lost connection

"Due to user request" suggests to me that the client (in this case, IIS or
.NET) is timing out waiting for a response and cancelling the query.

The documentation for Npgsql seems to support that:
http://npgsql.projects.postgresql.org/docs/manual/UserManual.htm (search for
'Cancelling a command in progress').

--
Brandon Aiken
CS/IT Systems Engineer
________________________________________
From: pgsql-novice-owner(at)postgresql(dot)org
[mailto:pgsql-novice-owner(at)postgresql(dot)org] On Behalf Of Frances Collier
Sent: Friday, September 29, 2006 4:02 PM
To: pgsql-novice(at)postgresql(dot)org
Subject: [NOVICE] Cancelled statement due to lost connection

Hello,

I have implemented an ASP.Net page on one box that has successfully
connected to my PostgreSQL database on another. Both boxes are running
Windows Server 2003. I am using the Npgsql connector. Most of the time it
runs fine, but on one query I am getting a "canceling statement due to user
request" error (Code: 57014).  I figure the connection is timing out,
especially since running it through pgAdmin it takes 29375+31 ms. So, I set
the NpgsqlConnection CommandTimeout to 300. But it didn't help. I've run
through the PostgreSQL documentation, the postgresql.conf, and pg_hba.conf
(for good measure) trying to find where to set the connection time for
PostgreSQL. Can this be set? If so, what's the proper configuration for
that?

Thanks,

-Frances

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly