Francisco Reyes <[EMAIL PROTECTED]> writes: > Tom Lane writes: >> is the pg_dump or its backend consuming CPU, or just sitting?
> At 90% of my CPU. The pg_dump process, or the backend? > I have loggin set log_min_messages = info and log_statement = 'all'. > Right after I start the pg_dump there is a flury of activity, which I am > putting at http://public.natserv.net/pg_dump_log.txt, but very quickly it > stops producing any output to the log. The last query shown is SELECT classid, objid, refclassid, refobjid, deptype FROM pg_depend WHERE deptype != 'p' ORDER BY 1,2 so apparently something is fishy about the dependency data. Can you execute this query by hand and get results? It could be that pg_depend is corrupted in a way that locks up the backend trying to read it, or it could be that pg_dump is getting confused and going into a loop trying to process the data. I can't tell from this description. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
