From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Krasimir Hristozov \(InterMedia Ltd\)" <krasi(at)imedia-dev(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: INSERT performance deteriorates quickly during a large import |
Date: | 2007-11-08 18:01:59 |
Message-ID: | 28007.1194544919@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Krasimir Hristozov \(InterMedia Ltd\)" <krasi(at)imedia-dev(dot)com> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Kent Miller | 2007-11-08 18:21:25 | Accessing a db with pgAdmin |
Previous Message | Tom Lane | 2007-11-08 17:54:43 | Re: what is the date format in binary query results |