{"push_id":2843791023,"size":6,"distinct_size":1,"ref":"refs/heads/commitfest/19/1530","head":"f70e97884cfa39cfc3276111f798679a261f5e7d","before":"3089a83275be41714f6813d5b24c5e7d56edad06","commits":[{"sha":"ab0ed6153a58294143d6d66ec5f3471477c59d57","author":{"name":"Noah Misch","email":"1db01d43e08596f43a65fb393d969b98ee5b4dc6@leadboat.com"},"message":"Ignore server-side delays when enforcing wal_sender_timeout.\n\nHealthy clients of servers having poor I/O performance, such as\nbuildfarm members hamster and tern, saw unexpected timeouts.  That\ndisagreed with documentation.  This fix adds one gettimeofday() call\nwhenever ProcessRepliesIfAny() finds no client reply messages.\nBack-patch to 9.4; the bug's symptom is rare and mild, and the code all\nmoved between 9.3 and 9.4.\n\nDiscussion: https://postgr.es/m/20180826034600.GA1105084@rfd.leadboat.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/ab0ed6153a58294143d6d66ec5f3471477c59d57"},{"sha":"ec74369931687885cfb6ce9dac55deefdb410086","author":{"name":"Alexander Korotkov","email":"1c137998207470ad0f56303c4fc305487ec0232f@postgresql.org"},"message":"Implement \"pg_ctl logrotate\" command\n\nCurrently there are two ways to trigger log rotation in logging collector\nprocess: call pg_rotate_logfile() SQL-function or send SIGUSR1 signal directly\nto logging collector process.  However, it's nice to have more suitable way\nfor external tools to do that, which wouldn't require SQL connection or\nknowledge of logging collector pid.  This commit implements triggering log\nrotation by \"pg_ctl logrotate\" command.\n\nDiscussion: https://postgr.es/m/20180416.115435.28153375.horiguchi.kyotaro%40lab.ntt.co.jp\nAuthor: Kyotaro Horiguchi, Alexander Kuzmenkov, Alexander Korotkov","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/ec74369931687885cfb6ce9dac55deefdb410086"},{"sha":"5e8d670c313531c0dca245943fb84c94a477ddc4","author":{"name":"Thomas Munro","email":"1ff054ef0838bf068a4b7c40eef026e560a37025@postgresql.org"},"message":"Add Greek characters to unaccent.rules.\n\nAuthor: Tasos Maschalidis\nReviewed-by: Michael Paquier, Tom Lane\nDiscussion: https://postgr.es/m/153495048900.1368.11566580687623014380%40wrigleys.postgresql.org\nDiscussion: https://postgr.es/m/VI1PR01MB38537EBD529FE5EE3FE9A5FEB5370%40VI1PR01MB3853.eurprd01.prod.exchangelabs.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/5e8d670c313531c0dca245943fb84c94a477ddc4"},{"sha":"44cac9346479d4b0cc9195b0267fd13eb4e7442c","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Avoid using potentially-under-aligned page buffers.\n\nThere's a project policy against using plain \"char buf[BLCKSZ]\" local\nor static variables as page buffers; preferred style is to palloc or\nmalloc each buffer to ensure it is MAXALIGN'd.  However, that policy's\nbeen ignored in an increasing number of places.  We've apparently got\naway with it so far, probably because (a) relatively few people use\nplatforms on which misalignment causes core dumps and/or (b) the\nvariables chance to be sufficiently aligned anyway.  But this is not\nsomething to rely on.  Moreover, even if we don't get a core dump,\nwe might be paying a lot of cycles for misaligned accesses.\n\nTo fix, invent new union types PGAlignedBlock and PGAlignedXLogBlock\nthat the compiler must allocate with sufficient alignment, and use\nthose in place of plain char arrays.\n\nI used these types even for variables where there's no risk of a\nmisaligned access, since ensuring proper alignment should make\nkernel data transfers faster.  I also changed some places where\nwe had been palloc'ing short-lived buffers, for coding style\nuniformity and to save palloc/pfree overhead.\n\nSince this seems to be a live portability hazard (despite the lack\nof field reports), back-patch to all supported versions.\n\nPatch by me; thanks to Michael Paquier for review.\n\nDiscussion: https://postgr.es/m/1535618100.1286.3.camel@credativ.de","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/44cac9346479d4b0cc9195b0267fd13eb4e7442c"},{"sha":"4299c32316addaad2255e6363b26ba1eec5c3999","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Doc: fix oversights in \"Client/Server Character Set Conversions\" table.\n\nThis table claimed that JOHAB could be used as a server encoding, which\nwas true originally but hasn't been true since 8.3.  It also lacked\nentries for EUC_JIS_2004 and SHIFT_JIS_2004.\n\nJOHAB problem noted by Lars Kanis, the others by me.\n\nDiscussion: https://postgr.es/m/c0f514a1-b7a9-b9ea-1c02-c34aead56c06@greiz-reinsdorf.de","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/4299c32316addaad2255e6363b26ba1eec5c3999"},{"sha":"f70e97884cfa39cfc3276111f798679a261f5e7d","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 19/1530] Speed up WAL file removal during recovery\n\nThis commit was automatically generated by cfbot at commitfest.cputube.org.\nIt is based on patches submitted to the PostgreSQL mailing lists and\nregistered in the PostgreSQL Commitfest application.\n\nThis branch will be overwritten each time a new patch version is posted to\nthe email thread, and also periodically to check for bitrot caused by changes\non the master branch.\n\nCommitfest entry: https://commitfest.postgresql.org/19/1530\nPatch(es): https://www.postgresql.org/message-id/0A3221C70F24FB45833433255569204D1F81B0C8@G01JPEXMBYT05\nAuthor(s): Takayuki Tsunakawa","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/f70e97884cfa39cfc3276111f798679a261f5e7d"}]}
{"actor":{"display_login":"postgresql-cfbot"}}