On Wed, Dec 30, 2015 at 10:31 PM, Shay Rojansky <r...@roji.org> wrote:
> OK, I finally found some time to dive into this. > > The backends seem to hang when the client closes a socket without first > sending a Terminate message - some of the tests make this happen. I've > confirmed this happens with 9.5rc1 running on Windows (versions 10 and 7), > but this does not occur on Ubuntu 15.10. The client runs on Windows as well > (although I doubt that's important). > > In case it helps, here's a gist > <https://gist.github.com/roji/33df4e818c5d64a607aa> with some .NET code > that uses Npgsql 3.0.4 to reproduce this. > > I am trying to setup an environment to reproduce this issue. I have installed Npgsql as below: PM> Install-Package Npgsql -Version 3.0.4 Installing 'Npgsql 3.0.4'. Successfully installed 'Npgsql 3.0.4'. Now, I am trying to use program.cs present in the above link, but it is neither printing any error nor able to perform any action. I have just created program.cs file as mentioned by you in one of the test folders and then trying to run it via: >program.cs "Host=localhost;Username=amit;Database=postgres" This program neither prints any error, nor I think it does any action. Can you guide me in reproducing the issue? I have tried to close/kill the psql client in various ways (closing the window/ End Process), but it works as expected. So I think it is important to reproduce it via Npgsql. Also I am trying this on latest PostgreSQL code (9.6 version code), but I think that doesn't matter because once I am able to execute this program successfully, I can even use 9.5 line to see the issue if it is not reproducible on 9.6. I am using Win-7 and Visual Studio 2010. With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
