Jose Vicente Nunez Z <josevnz@newbreak.com> writes:
> For that i'm using the PostgreSQL copy tool, but the problem is that is
> taking almost 9 hours to load the data:
Hmm, 889 rows/second doesn't sound that bad, considering that you've
given us no data about the hardware you're running on. In particular,
what's your disk setup?
But at any rate, the only bottlenecks I could think of for a COPY
command are:
1. Data conversion. This would depend on the column datatypes of the
table, which you didn't tell us.
2. Index updating. This would depend on the indexes on the table,
which you didn't tell us.
3. Foreign-key constraint checking. This would depend on the foreign
keys the table has, which you didn't tell us.
In short ... you'd better provide a lot more detail if you want
useful commentary.
> I apologize if this not the proper place to post this questions.
pgsql-performance would be more appropriate, probably.
regards, tom lane
