{"push_id":814842148,"size":1,"distinct_size":1,"ref":"refs/heads/REL9_2_STABLE","head":"ebc7d928a761a6e1d56fc23caf1079722821dc0e","before":"fd3e3cf500de7f8f625744fbd8a413b27f500abe","commits":[{"sha":"ebc7d928a761a6e1d56fc23caf1079722821dc0e","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Further twiddling of nodeHash.c hashtable sizing calculation.\n\nOn reflection, the submitted patch didn't really work to prevent the\nrequest size from exceeding MaxAllocSize, because of the fact that we'd\nhappily round nbuckets up to the next power of 2 after we'd limited it to\nmax_pointers.  The simplest way to enforce the limit correctly is to\nround max_pointers down to a power of 2 when it isn't one already.\n\n(Note that the constraint to INT_MAX / 2, if it were doing anything useful\nat all, is properly applied after that.)","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/ebc7d928a761a6e1d56fc23caf1079722821dc0e"}]}