{"push_id":2467283513,"size":3,"distinct_size":1,"ref":"refs/heads/commitfest/17/713","head":"adde78e2cd36975b47a91853157d923a3e90a136","before":"1c1fbe8f5ecf17c0c7f9a6e136ab9b8137320b65","commits":[{"sha":"893e9e65402e79cc5eb865825be32f675d8a72b2","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Doc: clarify explanation of pg_dump usage.\n\nThis section confusingly used both \"infile\" and \"outfile\" to refer\nto the same file, i.e. the textual output of pg_dump.  Use \"dumpfile\"\nfor both cases, per suggestion from Jonathan Katz.\n\nDiscussion: https://postgr.es/m/152311295239.31235.6487236091906987117@wrigleys.postgresql.org","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/893e9e65402e79cc5eb865825be32f675d8a72b2"},{"sha":"b3b7f7898f17009912b3fc16620d042ec8482557","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix additional breakage in covering-index patch.\n\nCheckIndexCompatible() misused ComputeIndexAttrs() by not bothering\nto fill ii_NumIndexAttrs and ii_NumIndexKeyAttrs in the passed\nIndexInfo.  Omission of ii_NumIndexAttrs was previously unimportant,\nbut now this matters because ComputeIndexAttrs depends on\nii_NumIndexKeyAttrs to decide how many columns it needs to report on.\n\n(BTW, the fact that this oversight wasn't detected earlier implies\nthat we have no regression test verifying whether CheckIndexCompatible\never succeeds.  Bad dog.  Not the job of this patch to fix it, though.)\n\nAlso, change the API of ComputeIndexAttrs so that it fills the opclass\noutput array for all column positions, as it does for the options output\narray; positions for non-key index columns are filled with zeroes.\nThis isn't directly fixing any bug, but it seems like a good idea.\n\nPer valgrind failure reports from buildfarm.\n\nAlexander Korotkov, tweaked a bit by me\n\nDiscussion: https://postgr.es/m/CAPpHfduWrysrT-qAhn+3Ea5+Mg6Vhc-oA6o2Z-hRCPRdvf3tiw@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/b3b7f7898f17009912b3fc16620d042ec8482557"},{"sha":"adde78e2cd36975b47a91853157d923a3e90a136","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 17/713] Correct space parsing in to_timestamp()\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/713\nPatch(es): https://www.postgresql.org/message-id/20180217090239.GA14632%40arthur.localdomain\nAuthor(s): Arthur Zakirov","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/adde78e2cd36975b47a91853157d923a3e90a136"}]}
{"actor":{"display_login":"postgresql-cfbot"}}