Обсуждение: pgAdminII 1.4.12 crash with PostgreSQL 7.3
Hi,
My PostgreSQL 7.3 setup seems to crash all versions of pgAdminII (tested
versions : 1.2, 1.4.2, 1.4.12), immediately after pgAdmin2 connects to
the database.
(Connections to pre-7.3 PostgreSQL db's work OK).
I tested this on both WinME and Win2K/SP3, with both an older and the
most recent psqlODBC version (07.02.0005).
PostgreSQL is the version from RedHat RawHide (postgresql-7.3-2). I
tried both my upgraded 7.2 databases, and a freshly created one ('initdb').
Please note I can connect and execute queries using the psql console.
Transcript from a pgAdmin2 connect session :
Dec 22 22:19:12 lmb042 postgres[3041]: [1] LOG: connection received:
host=172.16.117.129 port=1128
Dec 22 22:19:12 lmb042 postgres[3041]: [2] LOG: connection authorized:
user=postgres database=template1
Dec 22 22:19:12 lmb042 postgres[3041]: [3] LOG: query: select version()
Dec 22 22:19:12 lmb042 postgres[3041]: [4] LOG: duration: 0.000920 sec
Dec 22 22:19:12 lmb042 postgres[3041]: [5] LOG: query: set DateStyle to
'ISO'
Dec 22 22:19:12 lmb042 postgres[3041]: [6] LOG: duration: 0.000896 sec
Dec 22 22:19:12 lmb042 postgres[3041]: [7] LOG: query: set geqo to 'OFF'
Dec 22 22:19:12 lmb042 postgres[3041]: [8] LOG: duration: 0.000228 sec
Dec 22 22:19:12 lmb042 postgres[3041]: [9] LOG: query: select oid from
pg_type where typname='lo'
Dec 22 22:19:12 lmb042 postgres[3041]: [10] LOG: duration: 0.002523 sec
Dec 22 22:19:12 lmb042 postgres[3041]: [11] LOG: query: select
pg_client_encoding()
Dec 22 22:19:12 lmb042 postgres[3041]: [12] LOG: duration: 0.000511 sec
Dec 22 22:19:12 lmb042 postgres[3041]: [13] LOG: query: SELECT version()
Dec 22 22:19:12 lmb042 postgres[3041]: [14] LOG: duration: 0.002683 sec
Dec 22 22:19:12 lmb042 postgres[3041]: [15] LOG: query: SELECT
datlastsysoid FROM pg_database WHERE datname = 'template1'
Dec 22 22:19:12 lmb042 postgres[3041]: [16] LOG: duration: 0.005259 sec
Dec 22 22:19:17 lmb042 postgres[3041]: [17] LOG: pq_recvbuf: recv()
failed: Connection reset by peer
Executing query [15] in psql yields :
template1=# SELECT datlastsysoid FROM pg_database WHERE datname =
'template1';
datlastsysoid
---------------
16974
(1 row)
HTH.
This is a major PITA, as I expected to migrate my Access2000 database to
PostgreSQL 7.3. :-/
Kind regards,
Didier
--
Didier Moens
-----
RUG/VIB - Dept. Molecular Biomedical Research - Core IT
tel ++32(9)2645309 fax ++32(9)2645348
http://www.dmb.rug.ac.be
> -----Original Message----- > From: Didier Moens [mailto:moensd@xs4all.be] > Sent: 22 December 2002 21:48 > To: pgadmin-support@postgresql.org > Subject: [pgadmin-support] pgAdminII 1.4.12 crash with PostgreSQL 7.3 > > > > Hi, > > > My PostgreSQL 7.3 setup seems to crash all versions of > pgAdminII (tested > versions : 1.2, 1.4.2, 1.4.12), immediately after pgAdmin2 > connects to > the database. > (Connections to pre-7.3 PostgreSQL db's work OK). > Strange, is there anything odd about your PostgreSQL installation? What platform, configure options etc? Also, can you please send me a pgAdmin full debug log of the error occuring. You can enable looging under Tools -> Options. Regards, Dave.
Hi Dave, A merry Christmas to you (and your beloved ones), and all pgAdmin developers. Dave Page wrote: >Hi Didier, > >Glad it's working now. It might be worth mentioning in your report, that >the error appears to be coming from MDAC rather than pgAdmin. It appears >the MDAC (or a component of it that pgAdmin uses) is being destroyed for >some reason. The error message you are getting is basically the same as >you get from an app when you are debugging a COM object in VB that the >app is using, and you stop the debug. > I filed a bug report with RedHat : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=80394 It would be much appreciated, if you can add your comments (as I'm not a VB developer). On a related note : 1. Access2K database migration with 1.4.12 is approx. 6 to 8 times slower than previous versions (20 minutes -> over two hours), mainly in the Foreign Key creation, it seems. I'll check if this is due to pgAdmin (1.4.0 -> 1.4.12) or PostgreSQL (7.2.x -> 7.3). 2. Total migration execution time doesn't wrap around : ... Creating Foreign Key: invoicesstock Creating Foreign Key: ordersstock Creating Foreign Key: balancessubjobs3 Creating Foreign Key: budgetssubjobs3 Migration finished at: 24/12/2002 0:20:16, taking -77438,65 seconds. 3. The 'default values' of my Access2K fields do not get migrated : is this a bug or a missing feature ? Kind regards, Didier -- Didier Moens ----- RUG/VIB - Dept. Molecular Biomedical Research - Core IT tel ++32(9)2645309 fax ++32(9)2645348 http://www.dmb.rug.ac.be
Comments below prefixed DP. _____________Original message ____________ Subject: Re: [pgadmin-support] pgAdminII 1.4.12 crash with PostgreSQL 7.3 Sender: "Didier Moens" <moensd@xs4all.be> Date: Thu, 26 Dec 2002 15:23:13 +0000 Hi Dave, A merry Christmas to you (and your beloved ones), and all pgAdmin developers. DP: Thanks, and to you as well. Dave Page wrote: >Hi Didier, > >Glad it's working now. It might be worth mentioning in your report, that >the error appears to be coming from MDAC rather than pgAdmin. It appears >the MDAC (or a component of it that pgAdmin uses) is being destroyed for >some reason. The error message you are getting is basically the same as >you get from an app when you are debugging a COM object in VB that the >app is using, and you stop the debug. > I filed a bug report with RedHat : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=80394 It would be much appreciated, if you can add your comments (as I'm not a VB developer). DP: I'll take a look. On a related note : 1. Access2K database migration with 1.4.12 is approx. 6 to 8 times slower than previous versions (20 minutes -> over two hours), mainly in the Foreign Key creation, it seems. I'll check if this is due to pgAdmin (1.4.0 -> 1.4.12) or PostgreSQL (7.2.x -> 7.3). DP: Check you have logging set to none or errors only. The code has had few changes. 2. Total migration execution time doesn't wrap around : ... Creating Foreign Key: invoicesstock Creating Foreign Key: ordersstock Creating Foreign Key: balancessubjobs3 Creating Foreign Key: budgetssubjobs3 Migration finished at: 24/12/2002 0:20:16, taking -77438,65 seconds. DP: Odd, VB doesn't wrap values like C etc, you get an overflow error instead. 3. The 'default values' of my Access2K fields do not get migrated : is this a bug or a missing feature ? DP: Defaults are always problematic, not just due syntax differences in expressions. Iirc, in ADO we can't even see the defaultsfor most oledb providers, so we don't migrate them Regards, Dave.
Hi, Dave Page wrote: >Comments below prefixed DP. > >1. Access2K database migration with 1.4.12 is approx. 6 to 8 times >slower than previous versions (20 minutes -> over two hours), mainly in >the Foreign Key creation, it seems. I'll check if this is due to pgAdmin >(1.4.0 -> 1.4.12) or PostgreSQL (7.2.x -> 7.3). > >DP: Check you have logging set to none or errors only. The code has had few changes. > Yes, I made sure logging was set to none. I ran my tests again, connecting to a PostgreSQL 7.2.2 server (as to rule out any luring problems with 7.3) : When migrating my standard Access2K app (about 20 tables, some 100K records in total, nothing fancy), - pgAdminII 1.4.12 took approx. 35 minutes to migrate the tables and create the indexes, before starting to create the foreign keys. After another 40 minutes, I stopped the app (as I already knew total execution time would be more than 2 hours) ; - pgAdminII 1.4.0 took approx. 19 minutes for tables and indexes, and another 2 minutes for the foreign keys, totalling 21 minutes. I could test 1.4.1 and 1.4.2, if you'd like. Regards, Didier -- Didier Moens ----- RUG/VIB - Dept. Molecular Biomedical Research - Core IT tel ++32(9)2645309 fax ++32(9)2645348 http://www.dmb.rug.ac.be
> -----Original Message----- > From: Didier Moens [mailto:moensd@xs4all.be] > Sent: 26 December 2002 21:52 > To: Dave Page > Cc: pgadmin-support@postgresql.org > Subject: Re: [pgadmin-support] pgAdminII 1.4.12 crash with > PostgreSQL 7.3 > > > Hi, > > Dave Page wrote: > > >Comments below prefixed DP. > > > >1. Access2K database migration with 1.4.12 is approx. 6 to 8 times > >slower than previous versions (20 minutes -> over two > hours), mainly in > >the Foreign Key creation, it seems. I'll check if this is > due to pgAdmin > >(1.4.0 -> 1.4.12) or PostgreSQL (7.2.x -> 7.3). > > > >DP: Check you have logging set to none or errors only. The > code has had > >few changes. > > > > Yes, I made sure logging was set to none. > > I ran my tests again, connecting to a PostgreSQL 7.2.2 server (as to > rule out any luring problems with 7.3) : > When migrating my standard Access2K app (about 20 tables, some 100K > records in total, nothing fancy), > > - pgAdminII 1.4.12 took approx. 35 minutes to migrate the tables and > create the indexes, before starting to create the foreign keys. After > another 40 minutes, I stopped the app (as I already knew > total execution > time would be more than 2 hours) ; > > - pgAdminII 1.4.0 took approx. 19 minutes for tables and indexes, and > another 2 minutes for the foreign keys, totalling 21 minutes. > > > I could test 1.4.1 and 1.4.2, if you'd like. Weird, there have only been 3 commits between those versions (http://cvs.pgadmin.org/cgi-bin/viewcvs.cgi/pgadmin2/plugins/migration/f rmWizard.frm.diff?r1=text&tr1=1.18&r2=text&tr2=1.21&diff_format=h): 1.4.0 & 1.4.1 shipped with the same version of the main code (1.18, frmWizard.frm) 1.4.12 had one change - 'Create Serials as int8' And there have been 2 more changes since then: 'Create objects in the correct schema.' and 'Allow long FKey names in PostgreSQL 7.3+'. None of these changes should have a major effect on the speed. When you switched off logging, did you restart pgAdmin? The psqlODBC logging won't switch off until after a restart. Regards, Dave.