{"push_id":577251644,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"931bf3eb9b203ca02d729f5122a44cc250c27695","before":"2e105def09f27d49c1761abab06b427cfaa5d304","commits":[{"sha":"d17b6df239e6eebf288969e931cdbe8076d1fe12","author":{"email":"ac1e0af1ee8efe15f889b38482e897ff7d0f0432@iki.fi","name":"Heikki Linnakangas"},"message":"Fix knn-GiST queue comparison function to return heap tuples first.\n\nThe part of the comparison function that was supposed to keep heap tuples\nahead of index items was backwards. It would not lead to incorrect results,\nbut it is more efficient to return heap tuples first, before scanning more\nindex pages, when both have the same distance.\n\nAlexander Korotkov","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/d17b6df239e6eebf288969e931cdbe8076d1fe12"},{"sha":"931bf3eb9b203ca02d729f5122a44cc250c27695","author":{"email":"ac1e0af1ee8efe15f889b38482e897ff7d0f0432@iki.fi","name":"Heikki Linnakangas"},"message":"Fix a bug in pairing heap removal code.\n\nAfter removal, the next_sibling pointer of a node was sometimes incorrectly\nleft to point to another node in the heap, which meant that a node was\nsometimes linked twice into the heap. Surprisingly that didn't cause any\ncrashes in my testing, but it was clearly wrong and could easily segfault\nin other scenarios.\n\nAlso always keep the prev_or_parent pointer as NULL on the root node. That\nwas not a correctness issue AFAICS, but let's be tidy.\n\nAdd a debugging function, to dump the contents of a pairing heap as a\nstring. It's #ifdef'd out, as it's not used for anything in any normal\ncode, but it was highly useful in debugging this. Let's keep it handy for\nfurther reference.","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/931bf3eb9b203ca02d729f5122a44cc250c27695"}]}