From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Archiver not exiting upon crash |
Date: | 2012-05-21 16:22:32 |
Message-ID: | CAHGQGwFObS4C-_a6wQerj45FnJ_HZG=ByvkSJgvF6ftE0qL5dA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, May 19, 2012 at 1:23 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> I've been testing the crash recovery of REL9_2_BETA1, using the same
> method I posted in the "Scaling XLog insertion" thread. I have the
> checkpointer occasionally throw a FATAL error,
We should also fix this problem? If yes, could you show us the self-contained
test case to reproduce it?
> However, sometimes the automatic recovery never initiates. It looks
> like the postmaster is waiting for the archiver to exit before it
> starts recovery, and the archiver is waiting for something, I don't
> really know what.
Could you get the backtrace of the waiting archiver?
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
You might have gotten the following problem which was discussed before.
This problem was fixed in SIGQUIT signal handler of a backend, but ISTM
not that of an archiver.
http://archives.postgresql.org/pgsql-admin/2009-11/msg00088.php
Regards,
--
Fujii Masao
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-05-21 16:23:28 | Re: read() returns ERANGE in Mac OS X |
Previous Message | Tom Lane | 2012-05-21 16:19:27 | Re: release note item |