Christophe Pettus <xof@xxxxxxxxxxxx> writes: >> On Oct 9, 2017, at 13:01, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: >> Is that number changing at all? > Increasing: > AccessExclusiveLock | 8810 Oh, that's really interesting. So it's not *just* releasing locks but also acquiring them, which says that it is making progress of some sort. My bet is that the source server did something that's provoking O(N^2) behavior in the standby server's lock management. It's hard to say exactly what, but I'm wondering about something like a plpgsql function taking an AccessExclusiveLock inside a loop that repeatedly traps an exception. Can you correlate where the standby is stuck with what was happening on the source? regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
