Re: dropping connection

I was able to connect to a different database after I got the error.
However, now I could not get PgAdmin to crash.
After the first error, I connected to a different database with no problem.
Then I ran the query again, and got a slightly different error. Subsequent
runs of the query got the same error, but no crash.

The first error just said: ********** Error *******************
The second said: ********** Error ******************* no connection to
server.

On Mon, Jul 26, 2010 at 2:30 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:

> The former.
>
> On Monday, July 26, 2010, Michael Shapiro <mshapiro51(at)gmail(dot)com> wrote:
> > What do you mean: Can I select a different database after I get the
> error; or do I get the error using a different database?
> >
> >
> > On Mon, Jul 26, 2010 at 2:05 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> > On Mon, Jul 26, 2010 at 8:03 PM, Michael Shapiro <mshapiro51(at)gmail(dot)com>
> wrote:
> >> 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.
> >
> > I tried running the query a bunch of times. It errored, but didn't crash.
> >
> > Can you select a different database?
> >
> > --
> > Dave Page
> > EnterpriseDB UK: http://www.enterprisedb.com
> > The Enterprise Postgres Company
> >
> >
>
> --
> Dave Page
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise Postgres Company
>