On Fri, Dec 18, 2009 at 10:51 AM, Sigurgeir Gunnarsson
> The intention was never to talk down postgresql but rather trying to get
> some explanation of this difference so that I could do the proper changes.
> After having read the link from Euler's post, which I oversaw, I have
> managed to shorten the import time. My problem was with the indexes. I was
> able to shorten the import time, of a 26 million line import, from 2 hours +
> (I gave up after that time) downto 12 minutes by dropping the indexes after
> truncate and before copy.
> This is what I was expecting and I'm therefore satisfied with the result.
Ah ha! Well, it sounds like perhaps you have the answer to what was
causing the difference too, then. I'm not trying to be unhelpful,
just trying to explain honestly why you might not get exactly the
response you expect to MySQL comparisons - we only understand half of
In response to
pgsql-performance by date
|Next:||From: Tom Lane||Date: 2009-12-19 00:32:42|
|Subject: Re: Automatic optimization of IN clauses via INNER JOIN |
|Previous:||From: Robert Haas||Date: 2009-12-19 00:22:29|
|Subject: Re: Automatic optimization of IN clauses via INNER JOIN|