{"push_id":1782094299,"size":3,"distinct_size":3,"ref":"refs/heads/REL9_6_STABLE","head":"b8bd32a51f2dd451644175af7ae32f9bec3153f1","before":"ec504aff740993560d8d1ca16f70cbf8147cc622","commits":[{"sha":"b3d5b6833f460debde53a122709c3deb07056561","author":{"name":"Andres Freund","email":"c6cbfe878b4ee67646e7630734db67f536518d54@anarazel.de"},"message":"Have walsenders participate in procsignal infrastructure.\n\nThe non-participation in procsignal was a problem for both changes in\nmaster, e.g. parallelism not working for normal statements run in\nwalsender backends, and older branches, e.g. recovery conflicts and\ncatchup interrupts not working for logical decoding walsenders.\n\nThis commit thus replaces the previous WalSndXLogSendHandler with\nprocsignal_sigusr1_handler.  In branches since db0f6cad48 that can\nlead to additional SetLatch calls, but that only rarely seems to make\na difference.\n\nAuthor: Andres Freund\nReviewed-By: Michael Paquier\nDiscussion: https://postgr.es/m/20170421014030.fdzvvvbrz4nckrow@alap3.anarazel.de\nBackpatch: 9.4, earlier commits don't seem to benefit sufficiently","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/b3d5b6833f460debde53a122709c3deb07056561"},{"sha":"862204aaceb1199afeda96af9579e7cb553fe00b","author":{"name":"Andres Freund","email":"c6cbfe878b4ee67646e7630734db67f536518d54@anarazel.de"},"message":"Prevent possibility of panics during shutdown checkpoint.\n\nWhen the checkpointer writes the shutdown checkpoint, it checks\nafterwards whether any WAL has been written since it started and\nthrows a PANIC if so.  At that point, only walsenders are still\nactive, so one might think this could not happen, but walsenders can\nalso generate WAL, for instance in BASE_BACKUP and logical decoding\nrelated commands (e.g. via hint bits).  So they can trigger this panic\nif such a command is run while the shutdown checkpoint is being\nwritten.\n\nTo fix this, divide the walsender shutdown into two phases.  First,\ncheckpointer, itself triggered by postmaster, sends a\nPROCSIG_WALSND_INIT_STOPPING signal to all walsenders.  If the backend\nis idle or runs an SQL query this causes the backend to shutdown, if\nlogical replication is in progress all existing WAL records are\nprocessed followed by a shutdown.  Otherwise this causes the walsender\nto switch to the \"stopping\" state. In this state, the walsender will\nreject any further replication commands. The checkpointer begins the\nshutdown checkpoint once all walsenders are confirmed as\nstopping. When the shutdown checkpoint finishes, the postmaster sends\nus SIGUSR2. This instructs walsender to send any outstanding WAL,\nincluding the shutdown checkpoint record, wait for it to be replicated\nto the standby, and then exit.\n\nAuthor: Andres Freund, based on an earlier patch by Michael Paquier\nReported-By: Fujii Masao, Andres Freund\nReviewed-By: Michael Paquier\nDiscussion: https://postgr.es/m/20170602002912.tqlwn4gymzlxpvs2@alap3.anarazel.de\nBackpatch: 9.4, where logical decoding was introduced","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/862204aaceb1199afeda96af9579e7cb553fe00b"},{"sha":"b8bd32a51f2dd451644175af7ae32f9bec3153f1","author":{"name":"Andres Freund","email":"c6cbfe878b4ee67646e7630734db67f536518d54@anarazel.de"},"message":"Unify SIGHUP handling between normal and walsender backends.\n\nBecause walsender and normal backends share the same main loop it's\nproblematic to have two different flag variables, set in signal\nhandlers, indicating a pending configuration reload.  Only certain\nwalsender commands reach code paths checking for the\nvariable (START_[LOGICAL_]REPLICATION, CREATE_REPLICATION_SLOT\n... LOGICAL, notably not base backups).\n\nThis is a bug present since the introduction of walsender, but has\ngotten worse in releases since then which allow walsender to do more.\n\nA later patch, not slated for v10, will similarly unify SIGHUP\nhandling in other types of processes as well.\n\nAuthor: Petr Jelinek, Andres Freund\nReviewed-By: Michael Paquier\nDiscussion: https://postgr.es/m/20170423235941.qosiuoyqprq4nu7v@alap3.anarazel.de\nBackpatch: 9.2-, bug is present since 9.0","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/b8bd32a51f2dd451644175af7ae32f9bec3153f1"}]}
{"actor":{"display_login":"postgres-mirror"}}