On Thu, Feb 08, 2007 at 05:15:36PM -0500, Sven Willenberger wrote:
> prepareTableForCopy() function fire and the COPY command go. The table
> of 3 million rows finished copy from stdin fairly quickly but now the
> finishTableAfterCopy(115); analyze tablename has been "running" for some
> 40 minutes now; the only indexes on the thing are the primary key
> (two-column primary) and a single-column index (which "by hand" can be
> recreated in seconds). The cpu that this process has landed on is
> running at near 100% but a ktrace dumps nothing. Ideas?
Are there any ungranted locks? I assume it's trying to add indexes
back, and it might have a conflict?
A
--
Andrew Sullivan | [EMAIL PROTECTED]
"The year's penultimate month" is not in truth a good way of saying
November.
--H.W. Fowler
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
