Try using transactions. I found when doing single inserts they could take
hours, but when grouping all the inserts into a single transaction, it was
relatively quick. It's been a while, but I believe the syntax is:
BEGIN
insert ...
insert ...
insert ...
COMMIT;
At 11:15 AM 5/26/99, Michal Samek wrote:
>johan.granlund@solid.se wrote:
>>
>> As i dont know anything about triggers:)
>> Have you done a vacuum on the databases to clear out old transactions?
>
>I recreated the table, so I think there is not necessary to vacuum it
>(it takes unbelieveable amount of time); maybe when I'm filling the
>table by sending a lot of INSERT queries I should sometimes between
>inserts do a vacuum ? It looks strange for me.
>
>And many thanks for your help; I was thinking about dropping indexes and
>trigger, but It's impossible. Imagine this is not just a series of
>insert queries, the process I'm using is (simplicied): For each dbase
>record (the catalogue from the music label) to look-up if exist and if
>so, update; if no, insert. So I can't drop indexes which are needed by
>look-up function; nor can't drop trigger because it tracks inserts /
>updates of my table.
>I'm testing to group inserts / updates to blocks enclosed with
>transaction BEGIN; END;, but it now looks that it will help only little.
>
>PS I plan to rewrite the whole thing to Mysql (even it's no triggers, it
>will be harder but possible of course) and to report the result here if
>will be interesting)
>
>
>--
>Michal Samek, Tony distribuce s.r.o.
>webmaster@tony.cz (++420659/321350)
>ICQ: 38607210
>
