> Hello i start yesterday afternoon a COPY command into a table.
> the file is 15 Mb
> i've set triggers before and after insert on the table
> the before trigger just perform data check.
> the after trigger update a 10 000 rows linked table.
>
> the COPY command runs all the night ad has not yet finished...........
>
> what is the problem????
>
> PostgreSQL 6.5.2 running on Pentium II debian server use 98% CPU...
I had a similar thing once, while compiling a program, it took the computer
28 hours to complete. (on a P200)
My best guess is is that it's still running, make a quick check that the
main
process is still running. The action you are doing requires not just alot of
CPU-power, but also a lot of HD-read and writes.
Another check you could do is to see if the database itself is growing,
to do this, look if the total disk-usage of the database is growing, if it
is, then you just gave a whole lot of work-load to the server.
If either of these 2 checks come up negative, then you crashed the server,
however my experience with PostgreSQL is, is that when it crashes,
CPU-usage drops, not rises....
with kind regards,
Joost Roeleveld
