Bugs
Search the entire project
This project's trackers
This project's forums
This project's tasks
This project's releases
This project's documents
This project's news
Project
People
Skill
Advanced search
Log In
|
New Account
Home
My Page
Projects
Code Snippets
Project Openings
Npgsql .Net Data Provider for Postgresql
Summary
Activity
Forums
Tracker
Lists
Tasks
Docs
Surveys
News
SCM
Files
[#1010426] Broken Connections
View Trackers
|
Bugs
|
Download .csv
|
Monitor
Date:
2008-07-08 15:47
Priority:
3
State:
Open
Submitted by:
Andreas Schönebeck (
aschoenebeck
)
Assigned to:
Nobody (None)
Npgsql Version:
None
Category:
Group:
Resolution:
None
Summary:
Broken Connections
Detailed description
Here we go once again,
The problems I described in an older help forum post entitled "Broken Connections (fixed test)" and the patch discussion in "Experimental Patch of Doom", are still there although it got better with jon hanna's patch (beta3) and some bugfixes in beta4. Although better, I'm still not confident enough to ship Npgsql beta 4 with our software. For some users who tested postgresql support this resulted in the following comments:
- "I have strange delays!" (because of hanging queries)
- "I get no data!" (because of exceptions in npgsql)
In the meantime I've rewritten my testcase program, which I am happy to include as an attachement. Its quite complex now. It runs database queries with thread concurrency, calling Thread.Abort() randomly. Parameters can be adjusted in the static Program class. You need to adjust at least "Connection" and "Query". Also adjust Abort Times to your Database speed and Query record count, for throwing aborts most randomly. Please use a query that returns a lot of records (50000+).
Strange behaviour I encountered in the test:
- Queries hanging, not returning any results.
- Stream seeking not supported exception.
- Unrecognised response type exception.
- Remote host closed connection exception.
- Before pressing Enter to exit the program running
"SELECT * FROM pg_stat_activity" shows lots of stale connections.
I think these problems should all be addressed before releasing any 2.0 final version. And it should have higher priority than any new features or wizards for VS.
Thanks again for doing a great job,
Andreas
BTW: PG 8.3 on Vista (local), .Net 2.0 on Vista, Npgsql 2.0 beta4
Followup
Message
Date: 2008-09-08 14:08
Sender:
Francisco Figueiredo jr.
Hi, Andreas!
I've added some fixes on cvs based on Josh's previous patch.
Please give it a try and let us know. They will be on Npgsql 2 RC2
Attached Files:
Attachments:
Program.cs
Changes:
Field
Old Value
Date
By
File Added
344: Program.cs
2008-07-08 15:47
aschoenebeck