Re: Help troubleshooting SubtransControlLock problems

From: Scott Frazer <sfrazer(at)couponcabin(dot)com>
To:
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Help troubleshooting SubtransControlLock problems
Date: 2018-03-08 18:31:02
Message-ID: CA+ey=akgR+kgFM7eOsXnyyMYPkrv-ba=GymR3wGLU-qHHPJ9uw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Mar 7, 2018 at 3:50 PM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
wrote:
>
> Scott Frazer wrote:
>
> > It's only happening on the read replicas, though. I've just set my
master
> > to handle all the traffic, but that's not really sustainable
>
> I failed to notice at start of thread that these were replicas. I
> suppose then you would have to be thinking about the range of XIDs in
> the primary server. Maybe you left some old transaction open, or an
> uncommitted prepared transaction there?
>
> If not, I suppose you're up for some "perf" profiling ...

I think you got it. I found a 2-day old transaction on the master server
that never closed. I had to pg_terminate_backend on it and the problem
seems to have cleared up.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2018-03-08 18:34:08 Re: Troubleshooting a segfault and instance crash
Previous Message Justin Pryzby 2018-03-08 18:26:29 circular wait not triggering deadlock ?