From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | nickf(at)ontko(dot)com |
Cc: | "pgsql-admin" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Database is slow, vacuum hangs |
Date: | 2002-03-01 21:16:00 |
Message-ID: | 1393.1015017360@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Nick Fankhauser" <nickf(at)ontko(dot)com> writes:
> The deletes were slow, but worked, so the tables are all empty now. I
> started the vacuum and let it run for 4 hours while I did other work & it
> never came back.
Is the vacuum actually running (accumulating any CPU time)? Or is it
just waiting on a lock held by one of those other guys?
> During this time, I noticed that two postmaster processes
> were constantly running- each taking up almost exactly half of the CPU time.
> There was no disk activity. After I canceled the vacuum, the two postmaster
> processes remained and continued to use all of the CPU time. (they're still
> there.)
And what are they doing --- who started them, what query was sent to
'em, etc?
If you haven't a clue, try attaching to each process with a debugger and
printing out the global variable debug_query_string.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Nick Fankhauser | 2002-03-01 21:47:48 | Re: Database is slow, vacuum hangs |
Previous Message | Nick Fankhauser | 2002-03-01 20:44:39 | Database is slow, vacuum hangs |