It is frustrating, it is not reproducible by me either. I can't find a way
to force it happen. I even had the sys-admins on the server kill the backend
process that was connected to the query window and could not get the crash.

I have had my system checked to see if there are hardware issues that may
cause this, but nothing has turned up.
I understand that if a problem is not reproducible it would be pretty hard
to find the cause.

Is there anything I can do on my end to help with this? Some kind of
debugging (either in PgAdmin or Windows) that I could turn on so that when
it does happen, you would have something useful to work with ...


On Mon, Sep 27, 2010 at 10:19 AM, Dave Page <dp...@pgadmin.org> wrote:

> On Sat, Sep 25, 2010 at 8:32 AM, Dave Page <dp...@pgadmin.org> wrote:
> > On Sat, Sep 25, 2010 at 8:22 AM, Guillaume Lelarge
> > <guilla...@lelarge.info> wrote:
> >> Le 24/09/2010 18:17, Michael Shapiro a écrit :
> >>> I am running the latest release for Windows (XP) -- 1.12.0 (Sep 17,
> 2010).
> >>> The SQL query window lost the connect, failed to reestablish it, and
> PgAdmin
> >>> crashed when I ran the query 2 more times.
> >>>
> >>> I had run a query that took about 10 minutes to complete. It completed.
> Then
> >>> I stepped away for a while, so I do not know how long to query window
> was
> >>> idle. When I returned, I ran the query again. I got an error, but no
> crash.
> >>> I ran it again and got an error, but no crash. The third time caused
> the
> >>> crash.
> >>> At no time did PgAdmin ask me to reconnect nor tell me it was trying to
> >>> reconnect.
> >>>
> >>
> >> Sorry, but I still can't reproduce this :-/
> >
> > I will be trying later - but note that the Query Tool intentionally
> > doesn't try to reconnect like the browser does, as we have no way of
> > reliably resetting the new connection to the state the old one was in.
>
> I can't reproduce it either.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise Postgres Company
>

Reply via email to