| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Cory Vokey" <cvokey(at)rim(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Lingering Checkpoint Process |
| Date: | 2005-02-23 18:12:53 |
| Message-ID: | 20647.1109182373@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Cory Vokey" <cvokey(at)rim(dot)com> writes:
> Hi all, I'm seeing a checkpoint process lingering around for ~ 24hrs on
> one of my test systems and WAL logs are accumulating. It's running
> postgres 7.4.6.
Is the checkpoint process actually doing anything, or just sitting?
(strace'ing it would reveal this) If it seems to be just sitting,
could you attach to it with gdb and get a stack trace to find out
where it's sitting?
The only known cause of checkpoints not proceeding in 7.4.* is that
long btree CREATE INDEX operations can block them. But 24 hours
sounds pretty long for a CREATE INDEX too ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cory Vokey | 2005-02-23 18:43:18 | Re: Lingering Checkpoint Process |
| Previous Message | John Jensen | 2005-02-23 18:08:30 | Re: Question |