{"push_id":2308386676,"size":4,"distinct_size":1,"ref":"refs/heads/commitfest/17/528","head":"3369a173dc072b21c8a5961ca3e4633f036c43c1","before":"f7f733bdc9dd159911300f8338e4295720005d51","commits":[{"sha":"a926eb84e07a604da6d059eca1fd87f919bb5d7a","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Ensure that all temp files made during pg_upgrade are non-world-readable.\n\npg_upgrade has always attempted to ensure that the transient dump files\nit creates are inaccessible except to the owner.  However, refactoring\nin commit 76a7650c4 broke that for the file containing \"pg_dumpall -g\"\noutput; since then, that file was protected according to the process's\ndefault umask.  Since that file may contain role passwords (hopefully\nencrypted, but passwords nonetheless), this is a particularly unfortunate\noversight.  Prudent users of pg_upgrade on multiuser systems would\nprobably run it under a umask tight enough that the issue is moot, but\nperhaps some users are depending only on pg_upgrade's umask changes to\nprotect their data.\n\nTo fix this in a future-proof way, let's just tighten the umask at\nprocess start.  There are no files pg_upgrade needs to write at a\nweaker security level; and if there were, transiently relaxing the\numask around where they're created would be a safer approach.\n\nReport and patch by Tom Lane; the idea for the fix is due to Noah Misch.\nBack-patch to all supported branches.\n\nSecurity: CVE-2018-1053","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/a926eb84e07a604da6d059eca1fd87f919bb5d7a"},{"sha":"1eb5d43beed9d8cdc61377867f0a53eb2cfba0c4","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Last-minute updates for release notes.\n\nSecurity: CVE-2018-1052, CVE-2018-1053","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/1eb5d43beed9d8cdc61377867f0a53eb2cfba0c4"},{"sha":"f069c91a5793ff6b7884120de748b2005ee7756f","author":{"name":"Robert Haas","email":"93159bdbbeed5b47be970d58edfbdf1c3ce55e4c@postgresql.org"},"message":"Fix possible crash in partition-wise join.\n\nThe previous code assumed that we'd always succeed in creating\nchild-joins for a joinrel for which partition-wise join was considered,\nbut that's not guaranteed, at least in the case where dummy rels\nare involved.\n\nAshutosh Bapat, with some wordsmithing by me.\n\nDiscussion: http://postgr.es/m/CAFjFpRf8=uyMYYfeTBjWDMs1tR5t--FgOe2vKZPULxxdYQ4RNw@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/f069c91a5793ff6b7884120de748b2005ee7756f"},{"sha":"3369a173dc072b21c8a5961ca3e4633f036c43c1","author":{"name":"Commitfest Bot","email":"aab6a594935fe5db0d690bc154b19f642bfbe9d7@cputube.org"},"message":"[CF 17/528] Fix the optimization to skip WAL-logging on table created in same transaction\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 or the master branch changes.\n\nCommitfest entry: https://commitfest.postgresql.org/17/528\nPatch(es): https://www.postgresql.org/message-id/20180111.170355.123986255.horiguchi.kyotaro%40lab.ntt.co.jp\nAuthor(s): Heikki Linnakangas, Michael Paquier, Kyotaro Horiguchi","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/3369a173dc072b21c8a5961ca3e4633f036c43c1"}]}
{"actor":{"display_login":"postgresql-cfbot"}}