From: | Michael Shapiro <mshapiro51(at)gmail(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Guillaume Lelarge <guillaume(at)lelarge(dot)info>, PgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: dropping connection |
Date: | 2010-07-26 19:03:33 |
Message-ID: | AANLkTikrNw9hFYQLXcOUEDtPJMow6+OJ8ci=-7Np58pA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
What happens is that the first time it does give an error. But the editor is
not useable. If I rerun the query a couple times, it can crash.
On Mon, Jul 26, 2010 at 1:58 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> On Mon, Jul 26, 2010 at 5:41 PM, Michael Shapiro <mshapiro51(at)gmail(dot)com>
> wrote:
> > I tested 1/12 beta. It has exactly the same problem. When the SQL editor
> > loses the connection, rerunning the query causes PgAdmin to crash.
>
> I can't reproduce that - it errors cleanly for me (which is why I
> didn't work on the Query Tool earlier):
>
> -- Executing query:
> select version()
> Total query runtime: 0 ms.
> 1 row retrieved.
>
> -- Executing query:
> select version()
> ********** Error **********
>
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
>
>
> -- Executing query:
> select version()
> ********** Error **********
>
> no connection to the server
>
>
> --
> Dave Page
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise Postgres Company
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2010-07-26 19:05:09 | Re: dropping connection |
Previous Message | Dave Page | 2010-07-26 18:58:31 | Re: dropping connection |