Re: Excessive PostmasterIsAlive calls slow down WAL redo
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Stephen Frost <sfrost@snowman.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Heikki Linnakangas <hlinnaka@iki.fi>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2018-04-06T16:39:29Z
Lists: pgsql-hackers
Hi, On 2018-04-06 07:39:28 -0400, Stephen Frost wrote: > While I tend to agree that it'd be nice to just make it cheaper, that > doesn't seem like something that we'd be likely to back-patch and I tend > to share Heikki's feelings that this is a performance regression we > should be considering fixing in released versions. I'm doubtful about fairly characterizing this as a performance bug. It's not like we've O(n^2) behaviour on our hand, and if your replay isn't of a toy workload normally that one syscall isn't going to make a huge difference because you've actual IO and such going on. I'm also doubtful that it's sane to just check every 32 records. There's records that can take a good chunk of time, and just continuing for another 31 records seems like a bad idea. Greetings, Andres Freund
Commits
-
Poll postmaster less frequently in recovery.
- 57dcc2ef3320 14.0 landed
-
Use signals for postmaster death on FreeBSD.
- f98b8476cd4a 12.0 landed
-
Use signals for postmaster death on Linux.
- 9f09529952ac 12.0 landed
-
Introduce a pipe between postmaster and each backend, which can be used to
- 89fd72cbf26f 9.2.0 cited