On Fri, Nov 13, 2009 at 12:17 PM, Michael Shapiro <mshapiro51@gmail.com> wrote:
> The issue for this list has always been that PgAdmin gracefully handle the
> lost connection, not that it was the cause of it.
Well we never really knew that until now (though some might have suspected it).
> On Fri, Nov 13, 2009 at 5:01 AM, Dave Page <dpage@pgadmin.org> wrote:
>>
>> On Fri, Nov 13, 2009 at 1:24 AM, Michael Shapiro <mshapiro51@gmail.com>
>> wrote:
>> > I tested this with psql. It does lose the connection as well, but it
>> > also re-establishes it.
>> > The failure says: could not receive data from the server: The system
>> > cannot find the path specified
>> > If I run the query again, it fails with this error: server closed the
>> > connection unexpectedly
>> > If I run the query one more time, it runs fine (which implies psql has
>> > reconnected)
>> > If I do this same scenario in PgAdmin, the final query causes PgAdmin to
>> > crash.
>>
>> OK, so there's something outside of pgAdmin causing the connection to
>> drop. Please consult the PostgreSQL lists for that - removing pgAdmin
>> from the equation minimises the possible causes, and makes it much
>> easier to track down any problems in the PG code or on your network.
>>
>> Regarding pgAdmin, clearly we need to work on further improvements to
>> the connection handling code to allow it to attempt a reconnect.
>> That's already on the todo, but seems like something that I could play
>> with on a long flight (such as the one I have on Monday :-p).
>>
>> --
>> Dave Page
>> EnterpriseDB UK: http://www.enterprisedb.com
>
>
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com