Hi, On 2019-02-13 23:21:39 -0800, Peter Geoghegan wrote: > There would occasionally be cases where ops > would find it useful to throttle WAL writing using their own terrible > kludge (it involved sending SIGSTOP to the WAL writer).
That can't have been the workaround - either you'd interrupt it while holding critical locks (in which case nobody could write WAL anymore), or you'd just move all the writing to backends, no? Greetings, Andres Freund
