Обсуждение: PgAdmin Bug: using verly large varchar (binary Data) -> always Crash when viewing Table
<p><font face="Arial" size="2">using verly large varchar (binary Data) -> always Crash when viewing Table</font><p><fontface="Arial" size="2">store 10 kb Files with bin2hex into varchar Column, 100 rows </font><p><font face="Arial"size="2">then try to look the Table, sometimes it works, sometimes mouse graphics destroyed,sometimes WindowsGUI destroyed.</font><br /><font face="Arial" size="2">try to scroll the Table or resize Windows or Cells, its crashsometimes.</font><p><font face="Arial" size="2">Crash -> cannot use Mouse or Keyboard, but Applikation in Windowswork fine. look like freezes</font><br /><font face="Arial" size="2">Crash -> Graphiccard stopped, no Screen, Monitor/TTFgoes offline</font><p><font face="Arial" size="2">but never Bluescreen Crash !!!!</font><p><font face="Arial"size="2">all Version tested 1.0 / 1.1 / 1.2 / 1.3 and lasted Version from</font> <font face="Courier New" size="2">19-Jun-2005</font><p><fontface="Arial" size="2">thx</font>
From: pgadmin-support-owner@postgresql.org [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of jan.dwinger@asinteractive.de
Sent: 06 July 2005 12:36
To: pgadmin-support@postgresql.org
Subject: [pgadmin-support] PgAdmin Bug: using verly large varchar (binary Data) -> always Crash when viewing Tableusing verly large varchar (binary Data) -> always Crash when viewing Table
store 10 kb Files with bin2hex into varchar Column, 100 rows
then try to look the Table, sometimes it works, sometimes mouse graphics destroyed,sometimes Windows GUI destroyed.
try to scroll the Table or resize Windows or Cells, its crash sometimes.Crash -> cannot use Mouse or Keyboard, but Applikation in Windows work fine. look like freezes
Crash -> Graphiccard stopped, no Screen, Monitor/TTF goes offlinebut never Bluescreen Crash !!!!
all Version tested 1.0 / 1.1 / 1.2 / 1.3 and lasted Version from 19-Jun-2005
First off, please bear in mind that the table viewer simply isn't designed for viewing such large amounts of data - if you need to view very large tables, you should use the view filtered data option and select only the rows you actually need. That said, it shouldn't really crash...
As I test, I just inserted 2000 rows containing a serial column and 124Kb of bin2hex output each into a table (by my reckoning, that's around 250MB of data. The table viewer worked without crashing, displaying all 2000 rows in around 10 seconds. Thats with pgAdmin and the server running on the same 2GHz laptop running XP Pro. I then did the same again with 60 rows of 300Kb each - again that worked, although it was horrendously slow that time.
What sort of hardware are you running on? What OS?
Regards, Dave.
From: jan.dwinger@asinteractive.de [mailto:jan.dwinger@asinteractive.de]
Sent: 07 July 2005 14:32
To: Dave Page
Subject: AW: [pgadmin-support] PgAdmin Bug: using verly large varchar (binary Data) -> always Crash when viewing TableThx for fast reply.Okay, we use Dell Computer ( P4 1.4 - 1-8 GHz / 256 MB - 512 MB ).Client Computer always running with Windows 2000 Pro SP4, all our Server running with Linux, of course.Background running Software always Outlook 2001 SP1 and McAfee McShield (old, old old)
Testing with 3 Win2k Client, all have the same Problem.First all Applikation Windows freeze, cannot move Mouse over bottom Taskborder, 5 second later Mouse freeze, Keyboard is dead.Look like a Problem with Win2k, no Error is logged by pgAdmin 1.3 (Jun 19 2005).than i stopped my Virus Scanner, stop Outlook and other running background Software, testing again.create a new Table test_varchar (id,files) and write 20 insertsinsert into test_varchar(files) values (repeat('4F',4001));...insert into test_varchar(files) values (repeat('4F',4020));funny, the Log show only max 1536 Bytes per Thread/Execution, cutting and some awful Characters "ã´Ä¡"I execute inserts above 50 times. Viewing Table View and execute inserts again with no Problem,but suddenly 2 Minutes later Screen goes blank, TFT goes Offline, PC crashed :(I put the last Lines from pgAdmin Log here.