| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: logical replication busy-waiting on a lock |
| Date: | 2017-05-29 18:38:20 |
| Message-ID: | CAMkU=1zjF3qm873Qj73rUfEaNOnzAE3E2QmTHbU6kaOUKY0-5A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, May 27, 2017 at 6:48 AM, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>
wrote:
>
>
> Actually, I guess it's the pid 47457 (COPY process) who is actually
> running the xid 73322726. In that case that's the same thing Masahiko
> Sawada reported [1].
Related, but not the same. It would be nice if they didn't block, but if
they do have to block, shouldn't it wait on a semaphore, rather than doing
a tight loop? It looks like maybe a latch didn't get reset when it should
have or something.
[1]
> https://www.postgresql.org/message-id/flat/CAD21AoC2KJdavS7MFffmSsRc1dn3V
> g_0xmuc%3DUpBrZ-_MUxh-Q%40mail.gmail.com
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-05-29 18:40:26 | Re: logical replication busy-waiting on a lock |
| Previous Message | Tom Lane | 2017-05-29 18:25:01 | Re: fix side-effect in get_qual_for_list() |