| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> |
| Subject: | Re: LogwrtResult contended spinlock |
| Date: | 2022-03-22 01:11:18 |
| Message-ID: | 20220322011118.nphl6bl3fegepj6w@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2021-11-22 18:56:43 -0300, Alvaro Herrera wrote:
> There was an earlier comment by Andres that asyncXactLSN should also be
> atomic, to avoid an ugly spinlock interaction with the new atomic-based
> logwrtResult. The 0002 here is an attempt at doing that; I found that
> it also needed to change WalWriterSleeping to use atomics, to avoid
> XLogSetAsyncXactLSN having to grab the spinlock for that.
This patch currently doesn't apply: http://cfbot.cputube.org/patch_37_2716.log
Are you aiming this for v15? Otherwise I'd like to move the entry to the next
CF. Marked as waiting-on-author.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-03-22 01:12:08 | Re: pg14 psql broke \d datname.nspname.relname |
| Previous Message | Euler Taveira | 2022-03-22 01:09:58 | Re: logical replication restrictions |