El jue, 08-11-2007 a las 13:01 -0500, Tom Lane escribió: > "Krasimir Hristozov \(InterMedia Ltd\)" <krasi@xxxxxxxxxxxxxx> writes: > > We need to import data from a relatively large MySQL database into an > > existing PostgreSQL database, using a PHP5 script that SELECTs from MySQL > > and INSERTs in PostgreSQL. A part of the import involves moving about > > 1,300,000 records from one MySQL table to one of our PostgreSQL tables. The > > problem is that the insert performance inevitably deteriorates as the number > > of inserts increases. > > Are you *certain* you've gotten rid of all the indexes and foreign keys? > A simple insert ought to be pretty much constant-time in Postgres, so it > seems to me that you've missed something. > > It also seems possible that you are wrong to disregard PHP as a possible > source of the problem. Have you tried watching the PHP and PG backend > processes with "top" (or similar tool) to see who's consuming CPU time > and/or memory space? > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings Hi for all, Why better try use PERL DBI, may be better than. -- Regards, Julio Cesar Sánchez González. -- Ahora me he convertido en la muerte, destructora de mundos. Soy la Muerte que se lleva todo, la fuente de las cosas que vendran. www.sistemasyconectividad.com.mx http://darkavngr.blogspot.com/ ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
