On 8/1/17 20:20, Andres Freund wrote: > Well, that's how it is for all bgworkers - maybe a better solution is to > adjust that message in the postmaster rather than fiddle with the worker > exist code? Seems like we could easily take pmStatus into account > inside LogChildExit() and set the log level to DEBUG1 even for > EXIT_STATUS_1 in that case? Additionally we probably should always log > a better message for bgworkers exiting with exit 1, something about > unregistering the worker or such.
Maybe it doesn't need to be logged at all (other than perhaps as DEBUG)? A few months ago, people were complaining about too many messages about background workers starting. Now we are having complaints about messages about background workers stopping. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
