Re: pgAdminII 1.1.66-Dev crash
Dave, thanks for your time sofar; >Well, I've loaded your database & can view every table with no problems on >my system. I am running the latest ODBC driver though (07.01.0009) - can you >try it from http://odbc.postgresql.org please. My system was running the 07.01.0008 version but upgrading to the newer version does not make any difference. >Also, do you have another client PC you can try, just to try to eliminate >anything server end - if not, you could try a dump/reload which might remove >any invalid characters (as might have been the case in the file you sent >me). Hmm; I actually have done this already before mailing, I have 2 different servers with 2 different workstations accessing the server. The only thing the 2 setups have in common is that the client is a W2K and the server runs FreeBSD 4.4-STABLE with Postgres 7.1.3 Transferred dumps from one server to another a number of times but that does not remove the problem either. However I just found out that the crash disappears after deleting random records until there are 3 or 4 left in the table. Perhaps there is a size limitation of ODBC which is reached. Will investigate further when I have more time, any suggestions from your end are more than welcome. Thanks -- Paul Jongsma WEBtic Internet Consultancy @ http://www.webtic.nl/
Re: pgAdminII 1.1.66-Dev crash
At 13:59 30-11-2001 +, Dave Page wrote: >It ships with VB - it's actually part of mscomctl.ocx which is the >'Microsoft Windows Common Controls 6.0'. What version do you have there (I >have 6.1.83.41)? 6.0.88.62 , worth an upgrade I assume, where can I find one? -- Paul Jongsma WEBtic Internet Consultancy @ http://www.webtic.nl/
No Subject
Re: pgAdminII 1.1.66-Dev crash
> -Original Message- > From: Paul Jongsma [mailto:[EMAIL PROTECTED]] > Sent: 30 November 2001 13:25 > To: Dave Page > Subject: RE: [pgadmin-support] pgAdminII 1.1.66-Dev crash > > > > Dave, > > >That doesn't overly surprise me. I suspect the MS Listview > control that > >pgAdmin uses is at fault - I have had trouble with it in the > past but I > >thought they fixed that. I'm *very* confident that it's not pgAdmin > >itself that's falling over, because the VB runtimes *always* catch > >coding errors and pgAdmin has extensive code to trap these and deal > >with them nicely. However a control such as the listview which is > >probably written in C++ probably has far less (and less > graceful)error > >handling. > > On my homemachine I have Visual Studio installed, and crashes > of pgAdmin activitate the debugger and now the infamous "Dr Watson". > > Any crash thusfar was in "kernel32.dll" and indicated an > address exception. > > Further tested things on my end; > > I made a simple "in the bubble" table containing 5 records, > if you would look at it in CSV format it would be: > > idx;title;intro;body;date;current > "1";"titel";"intro";"body";"26-05-2001";"" > "2";"titel";"intro";"body";"26-05-2001";"" > "3";"titel";"intro";"body";"26-05-2001";"" > "4";"titel";"intro";"body";"26-05-2001";"" > "5";"titel";"intro";"body";"26-05-2001";"" > > This table causes no problems whatsoever, create 1+ > entries and it will still work like a charm. > > However: extend the "body" field in record 5 to a > string of exactly 12137 bytes or more and the > problem will occur. Extract 1 byte and it will > be fine. > > The 5 records is completely arbitrary, the same > problem occurs with only 1 record in the table. > > This explains my earlier "random delete until it works", > I randomly deleted stuff until only records where > length(body)<12137 were left. > > Now how could I go and fix this? Is this Listview component > part of VB runtime or is it part of the Windows system? It ships with VB - it's actually part of mscomctl.ocx which is the 'Microsoft Windows Common Controls 6.0'. What version do you have there (I have 6.1.83.41)? /Dave.
Re: pgAdminII 1.1.66-Dev crash
> -Original Message- > From: Paul Jongsma [mailto:[EMAIL PROTECTED]] > Sent: 30 November 2001 11:59 > To: Dave Page > Cc: [EMAIL PROTECTED] > Subject: Re: [pgadmin-support] pgAdminII 1.1.66-Dev crash > > > > Dave, thanks for your time sofar; > > >Well, I've loaded your database & can view every table with > no problems > >on my system. I am running the latest ODBC driver though > (07.01.0009) - > >can you try it from http://odbc.postgresql.org please. > > My system was running the 07.01.0008 version but upgrading to > the newer version does not make any difference. > > >Also, do you have another client PC you can try, just to try to > >eliminate anything server end - if not, you could try a dump/reload > >which might remove any invalid characters (as might have > been the case > >in the file you sent me). > > Hmm; I actually have done this already before mailing, I have > 2 different servers with 2 different workstations accessing > the server. The only thing the 2 setups have in common is > that the client is a W2K and the server runs FreeBSD > 4.4-STABLE with Postgres 7.1.3 > > Transferred dumps from one server to another a number of > times but that does not remove the problem either. > > However I just found out that the crash disappears after > deleting random records until there are 3 or 4 left in the > table. Perhaps there is a size limitation of ODBC which is > reached. Will investigate further when I have more time, any > suggestions from your end are more than welcome. > Hmmm. There should be no problems with the ODBC driver in that sense - I often query 10s of thousands of records in the pgAdmin grid. I suspect there is one (or more) particular record in your table that it doesn't like and when you deleted most of the records you deleted those and left good ones. Could there be any non UK/US chars in your data, or any non-printables? Also, I assume all is OK with other large tables in your database? Perhaps you could write a quick script to populate a test table with a few 10s of thousands or rows for testing purposes. Regards, Dave.
