Use PostgresSigHupHandler in more places.
Robert Haas <rhaas@postgresql.org>
Use PostgresSigHupHandler in more places. There seems to be no reason for every background process to have its own flag indicating that a config-file reload is needed. Instead, let's just use ConfigFilePending for that purpose everywhere. Patch by me, reviewed by Andres Freund and Daniel Gustafsson. Discussion: http://postgr.es/m/CA+TgmoZwDk=BguVDVa+qdA6SBKef=PKbaKDQALTC_9qoz1mJqg@mail.gmail.com
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/postmaster/autovacuum.c | modified | +8 −22 |
| src/backend/postmaster/bgwriter.c | modified | +3 −17 |
| src/backend/postmaster/checkpointer.c | modified | +5 −19 |
| src/backend/postmaster/pgarch.c | modified | +5 −20 |
| src/backend/postmaster/pgstat.c | modified | +7 −21 |
| src/backend/postmaster/walwriter.c | modified | +3 −17 |
| src/backend/replication/logical/launcher.c | modified | +3 −20 |
| src/backend/replication/logical/worker.c | modified | +3 −20 |
Discussion
- global / super barriers (for checksums) 26 messages · 2018-10-30 → 2020-01-03