{"push_id":2311126228,"size":4,"distinct_size":1,"ref":"refs/heads/commitfest/16/1296","head":"f07dcbd4e6134ae6cd2954880d45949947b71cc4","before":"320db201ed7d80fdc7d5c1bc000059acc8561155","commits":[{"sha":"3785f7eee3d98bc0a7ac2576aac9c0be974217d4","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Doc: move info for btree opclass implementors into main documentation.\n\nUp to now, useful info for writing a new btree opclass has been buried\nin the backend's nbtree/README file.  Let's move it into the SGML docs,\nin preparation for extending it with info about \"in_range\" functions\nin the upcoming window RANGE patch.\n\nTo do this, I chose to create a new chapter for btree indexes in Part VII\n(Internals), parallel to the chapters that exist for the newer index AMs.\nThis is a pretty short chapter as-is.  At some point somebody might care\nto flesh it out with more detail about btree internals, but that is\nbeyond the scope of my ambition for today.\n\nDiscussion: https://postgr.es/m/23141.1517874668@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/3785f7eee3d98bc0a7ac2576aac9c0be974217d4"},{"sha":"9fafa413ac602624e10f61ef44a20c17029d43d8","author":{"name":"Robert Haas","email":"93159bdbbeed5b47be970d58edfbdf1c3ce55e4c@postgresql.org"},"message":"Avoid valgrind complaint about write() of uninitalized bytes.\n\nLogicalTapeFreeze() may write out its first block when it is dirty but\nnot full, and then immediately read the first block back in from its\nBufFile as a BLCKSZ-width block.  This can only occur in rare cases\nwhere very few tuples were written out, which is currently only\npossible with parallel external tuplesorts.  To avoid valgrind\ncomplaints, tell it to treat the tail of logtape.c's buffer as\ndefined.\n\nCommit 9da0cc35284bdbe8d442d732963303ff0e0a40bc exposed this problem\nbut did not create it.  LogicalTapeFreeze() has always tended to write\nout some amount of garbage bytes, but previously never wrote less than\none block of data in total, so the problem was masked.\n\nPer buildfarm members lousyjack and skink.\n\nPeter Geoghegan, based on a suggestion from Tom Lane and me.  Some\ncomment revisions by me.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/9fafa413ac602624e10f61ef44a20c17029d43d8"},{"sha":"23209457314f6fd89fcd251a8173b0129aaa95a2","author":{"name":"Robert Haas","email":"93159bdbbeed5b47be970d58edfbdf1c3ce55e4c@postgresql.org"},"message":"Fix incorrect grammar.\n\nEtsuro Fujita\n\nDiscussion: http://postgr.es/m/5A7981EA.8020201@lab.ntt.co.jp","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/23209457314f6fd89fcd251a8173b0129aaa95a2"},{"sha":"f07dcbd4e6134ae6cd2954880d45949947b71cc4","author":{"name":"Commitfest Bot","email":"aab6a594935fe5db0d690bc154b19f642bfbe9d7@cputube.org"},"message":"[CF 16/1296] Better estimate for filter cost\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/16/1296\nPatch(es): https://www.postgresql.org/message-id/CANE%2B7D9CJZc4RsJqq5oC7TptDyVPbrvex618deprGknkgsMqqA%40mail.gmail.com\nAuthor(s): Yuto Hayamizu, Ryoji Kawamichi","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/f07dcbd4e6134ae6cd2954880d45949947b71cc4"}]}
{"actor":{"display_login":"postgresql-cfbot"}}