From: | Christophe Pettus <xof(at)thebuild(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: startup process stuck in recovery |
Date: | 2017-10-09 19:21:34 |
Message-ID: | B7831B5D-4ED9-40FF-8E68-C28AA25319CC@thebuild.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Oct 9, 2017, at 12:18, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
> #0 0x0000558812f4f1da in ?? ()
> #1 0x0000558812f4f8cb in StandbyReleaseLockTree ()
> #2 0x0000558812d718ee in ?? ()
> #3 0x0000558812d75520 in xact_redo ()
> #4 0x0000558812d7f713 in StartupXLOG ()
> #5 0x0000558812f0e262 in StartupProcessMain ()
> #6 0x0000558812d8d4ea in AuxiliaryProcessMain ()
> #7 0x0000558812f0b2e9 in ?? ()
> #8 0x0000558812f0dae7 in PostmasterMain ()
> #9 0x0000558812d0c402 in main ()
The other observation is that the startup process is holding a *lot* of locks:
(pid 5882 is the startup process)
# select mode, count(*) from pg_locks where pid=5882 group by mode;
mode | count
---------------------+-------
ExclusiveLock | 1
AccessExclusiveLock | 7133
(2 rows)
--
-- Christophe Pettus
xof(at)thebuild(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Condor | 2017-10-09 19:36:14 | Question about memory usage of pg_dump |
Previous Message | Christophe Pettus | 2017-10-09 19:18:21 | Re: startup process stuck in recovery |