Matthew <matthew@xxxxxxxxxxx> writes:
> We have a process here that dumps a large quantity of data into an empty
> database, much like pg_restore, and then creates all the indexes at the
> end. In order to speed up that bit, I initially made it spawn off several
> threads, and make each thread run a CREATE INDEX operation in parallel.
> However, this resulted in random errors from Postgres - something to do
> with locked tables. So I changed it so that no two threads create indexes
> for the same table at once, and that solved it.
How long ago was that? There used to be some issues with two CREATE
INDEXes both trying to update the pg_class row, but I thought we'd fixed
it.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
