Re: Unhandled exception in PGAdmin when opening 16-million-record table - Mailing list pgsql-general

From Dave Page
Subject Re: Unhandled exception in PGAdmin when opening 16-million-record table
Date
Msg-id AANLkTikFcDtS_SQRp8+Hx+Ae_baRs26PS4T1ecahkgHy@mail.gmail.com
Whole thread Raw
In response to Re: Unhandled exception in PGAdmin when opening 16-million-record table  (Dmitriy Igrishin <dmitigr@gmail.com>)
Responses Re: Unhandled exception in PGAdmin when opening 16-million-record table  (Dmitriy Igrishin <dmitigr@gmail.com>)
List pgsql-general
On Sat, Oct 30, 2010 at 4:14 PM, Dmitriy Igrishin <dmitigr@gmail.com> wrote:
> Do you mean that cursors (regular, not holdable) live only inside a
> transactions?
> But it is possible to check transaction status from another part of pgAdmin
> or
> even make the window with result set modal ?

No, I mean that the tool was developed to help tune application
queries, in which the data transfer time can be just as important as
the query execution time. With cursors, you lose that information.

Of course, patches to make optional use of cursors would be interesting to us.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-general by date:

Previous
From: Dmitriy Igrishin
Date:
Subject: Re: Unhandled exception in PGAdmin when opening 16-million-record table
Next
From: Dmitriy Igrishin
Date:
Subject: Re: Unhandled exception in PGAdmin when opening 16-million-record table