tried to lock pg_class in the shorter index build transaction? Besides
seeming like a bad idea...
Wes
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
with rather restricted hardware (1GB memory, two
2-disk RAID 0's and a single disk). If the pilot proves what I think is
possible, and I can get real hardware (i.e. an intelligent caching array and
some serious memory), things change a bit.
Wes
---(end of broadcast
such that for each table it builds one
index by itself, then builds the remaining indexes in parallel. This
appears to be stable. I made several runs with no errors. I've got some
more testing to do, then I'll try my big run.
Thanks
Wes
---(end of broadcast
never know... CPU speed, hard drive speed (slow), etc.
Wes
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
initial attempts last night at duplicating it with a small result set
were not successful. I'll see what I can do.
On 4/25/06 3:25 AM, Zeugswetter Andreas DCP SD [EMAIL PROTECTED]
wrote:
Wes, you could most likely solve your immediate problem if you did an
analyze before
creating the indexes
On 4/25/06 9:58 AM, Tom Lane [EMAIL PROTECTED] wrote:
I can't think of any effect in the PG code that would make CREATE INDEX
commands tend to converge rather than diverge, so maybe there is some
external effect here. Wes, is your machine a dual processor by any
chance? Which OS X version
wait for termination
exit
As my test tables are small and indexing happens almost instantly, I put a
'sleep' after one of the forks so that the two don't complete at the same
time. When I do that, I don't get the errors.
Wes
---(end of broadcast
tried somewhat bigger test tables (a few rows
to a little over a hundred thousand). I can duplicate the error at will.
Wes
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
it to?
Of course, since your hardware is different, it may not show up since it
appears to be a timing thing.. I'm on a PB G4 1Ghz.
Wes
---(end of broadcast)---
TIP 6: explain analyze is your friend
