| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ashley Clark <aclark(at)ghoti(dot)org> |
| Cc: | Postgres General List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: VACUUM is hanging |
| Date: | 2001-05-04 16:45:23 |
| Message-ID: | 25702.988994723@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ashley Clark <aclark(at)ghoti(dot)org> writes:
> * Tom Lane in "Re: [GENERAL] VACUUM is hanging" dated 2001/05/04 11:09
> * wrote:
>> Since the PID mentioned by the postmaster is NOT the same one running
>> the vacuum, presumably this is just an indication that some other
>> backend finished its work and exited normally.
> I would agree except that this is a product in testing and there should
> be NOTHING accessing it at 4am.
The postmaster will be firing off periodic checkpoint subprocesses even
if there's no user activity. That's probably what those are.
>> It's unclear what the process doing the vacuum could be waiting for;
>> can you attach to it with gdb and get a backtrace?
> I'll try to recreate the situation and get a backtrace, if that's
> successful I guess I'll have to recompile with -g to get really useful
> information.
The backtrace might be useful even if it just shows routine names...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Burton | 2001-05-04 16:47:02 | Re: a primer on trigger? |
| Previous Message | Mihai Gheorghiu | 2001-05-04 16:45:02 | Varchar vs. text |