From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Michael Paesold" <mpaesold(at)gmx(dot)at> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Insert Performance |
Date: | 2002-09-25 22:06:55 |
Message-ID: | 28498.1032991615@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Michael Paesold" <mpaesold(at)gmx(dot)at> writes:
> To insert another 10562 rows takes about 12 minutes now!!!
> As I said I wrote a function to insert the rows (PL/pgSQL). All values were
> inserted inside a single function call; I always though that a function call
> would be executed inside a transaction block. Experience says it does.
Well, there's something fishy about your results. Using CVS tip I see
about a 4-to-1 difference between COPYing 10000 rows and INSERT'ing
10000 rows (as one transaction). That's annoyingly high, but it's still
way lower than what you're reporting ...
I used the contents of table tenk1 in the regression database for test
data, and dumped it out with "pg_dump -a" with and without -d. I then
just timed feeding the scripts to psql ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-09-25 22:11:29 | Re: CVS checkout errors |
Previous Message | Peter Eisentraut | 2002-09-25 22:06:38 | Re: CVS checkout errors |