Search Postgresql Archives

Re: Unhandled exception in PGAdmin when opening 16-million-record table

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hey all,

Why not to use MVC approach by implementing a model, which uses, e.g.
scrollable cursors? I believe that wxWidgets supports MVC.

2010/10/30 Peter Geoghegan <peter.geoghegan86@xxxxxxxxx>
On 29 October 2010 21:52, Rob Richardson <Rob.Richardson@xxxxxxxxxxx> wrote:
> A customer was reviewing the database that supports the application we have
> provided. One of the tables is very simple, but has over 16 million
> records. Here is the table's definition:
>
> CREATE TABLE feedback
> (
> Â charge integer,
> Â elapsed_time integer, -- number of elapsed minutes since data began
> recording
> Â tag_type character varying(24), -- Description of tag being recorded
> Â tag_value real, -- value of tag being recorded
> Â status smallint, -- PLC Status, recorded with Control PV only
> Â stack integer, -- Not used
> Â heating smallint DEFAULT 0, -- 1 for heating, 0 for cooling
> Â cooling smallint DEFAULT 0 -- not used
> )
>
> As you see, there is no primary key. There is a single index, as follows:
>
> CREATE INDEX feedback_charge_idx
> Â ON feedback
> Â USING btree
> Â (charge);
> In PGAdmin, the customer selected this table and clicked the grid on the
> toolbar, asking for all of the records in the table. After twenty minutes,
> a message box appeared saying that an unhandled exception had happened.
> There was no explanation of what the exception was.ÂÂThe database log does
> not contain any information about it. The PGAdmin display did show a number
> of records, leading me to believe that the errorÂhappened in PGAdmin rather
> than anywhere in PostGres.
>
> Can anyone explain what is happening?

Does WxWidgets/PgAdmin provide an overload of global operator new()
that follows the pre-standard C++ behaviour of returning a null ptr,
ala malloc()? C++ application frameworks that eschew exceptions often
do. This sounds like an unhandled std::bad_alloc exception.


Why don't we have some hard limit on the number of rows viewable in a
table? Would that really be so terrible?


--
Regards,
Peter Geoghegan

--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



--
// Dmitriy.



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux