Re: Lingering Checkpoint Process
От | Cory Vokey |
---|---|
Тема | Re: Lingering Checkpoint Process |
Дата | |
Msg-id | D93992E093AA034F8D6BED008B91614B01A077AB@XCH30YKF.rim.net обсуждение исходный текст |
Ответ на | Lingering Checkpoint Process ("Cory Vokey" <cvokey@rim.com>) |
Список | pgsql-admin |
Thanks for the response Tom. The checkpoint process seems to be just sitting. I'll post the details of strace/gdb in the morning. Thanks again! --Cory BIS Database Engineering -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Wednesday, February 23, 2005 1:13 PM To: Cory Vokey Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Lingering Checkpoint Process "Cory Vokey" <cvokey@rim.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 --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including materialprotected by the solicitor-client or other applicable privileges), or constitute non-public information. Any useof this information by anyone other than the intended recipient is prohibited. If you have received this transmissionin error, please immediately reply to the sender and delete this information from your system. Use, dissemination,distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
В списке pgsql-admin по дате отправления: