Re: pgAdminII 1.4.12 crash with PostgreSQL 7.3

> -----Original Message-----
> From: Didier Moens [mailto:moensd(at)xs4all(dot)be]
> Sent: 26 December 2002 21:52
> To: Dave Page
> Cc: pgadmin-support(at)postgresql(dot)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.