From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: backends stuck in "startup" |
Date: | 2017-11-21 23:40:27 |
Message-ID: | 20171121234027.b4n4jlsfda42qb6r@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
On 2017-11-21 17:09:26 -0600, Justin Pryzby wrote:
> I'm sorry to report this previously reported problem is happening again,
> starting shortly after pg_upgrading a customer to PG10.1 from 9.6.5.
>
> As $subject: backends are stuck in startup for minutes at a time. I didn't
> strace this time, but I believe last time I saw one was waiting in a futex.
Could you try stracing next time? Don't think it's conclusive that
they're all continually waiting rather than contending on a few locks.
As soon as you attach to one backend a contended lock situation can
quickly turn into standstill if you end up interrupting a process that
holds a lock.
> - we DO use temp tables; it looks like we created up to 90 temp tables each hour;
Doesn't quite seem enough to cause problems.
> - I'm planning do disable sync seqscan for the night (although as I understand
> that may not matter (?))
I doubt it matters here.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2017-11-21 23:45:58 | Re: backends stuck in "startup" |
Previous Message | Tom Lane | 2017-11-21 23:21:16 | Re: backends stuck in "startup" |