On Fri, Jul 19, 2024 at 10:22 AM Christoph Berg <m...@debian.org> wrote: > I'd argue this is exactly what I mean by "this system has a problem". > Telling the user about that makes sense.
That's a fair position. > > cautious about this than most people on this thread: log_checkpoints > > won't generate more than a few lines of output per checkpoint > > interval, and a checkpoint cycle will be on the order of minutes, so > > it's really never that much volume. On the other hand, in theory, this > > setting can generate arbitrarily many messages. > > Well, it's still limited by 1 message per second (times > max_connections). It won't suddenly fill up the server with 1000 > messages per second. You make it sound like running with max_connections=5000 is a bad idea. (That was a joke, but yes, people actually do this, and no, it doesn't go well.) > The log volume is the lesser of the problems. Not printing the message > just because the system does have a problem isn't the right fix. Yeah. > Let's fix the default. People who have a problem can still disable it, > but then everyone else gets the useful messages in the first iteration. Reasonable. -- Robert Haas EDB: http://www.enterprisedb.com
