{"push_id":1100397536,"size":6,"distinct_size":6,"ref":"refs/heads/master","head":"a89505fd21da337b81172871d8f65d9a4fa22a8b","before":"d136d600f9756232b36681fdfada0e40e1563a47","commits":[{"sha":"e324f8ad610bdc83a1392e54da5d9613e710b02f","author":{"email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net","name":"Peter Eisentraut"},"message":"Update config.guess and config.sub","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/e324f8ad610bdc83a1392e54da5d9613e710b02f"},{"sha":"64d60c8bf0703011d79dcb8a55dc42dcedc1e10f","author":{"email":"d3eaa418a359156a10c6383b2e3a44959960ecf6@snowman.net","name":"Stephen Frost"},"message":"Correct pg_dump WHERE clause for functions/aggregates\n\nThe query to grab the function/aggregate information is now joining\nto pg_init_privs, so we can simplify (and correct) the WHERE clause\nused to determine if a given function's ACL has changed from the\ninitial ACL on the function.\n\nBug found by Noah, patch by me.","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/64d60c8bf0703011d79dcb8a55dc42dcedc1e10f"},{"sha":"5d589993cad212f7d556d52cc1e42fe18f65b057","author":{"email":"d3eaa418a359156a10c6383b2e3a44959960ecf6@snowman.net","name":"Stephen Frost"},"message":"pg_dump performance and other fixes\n\nDo not try to dump objects which do not have ACLs when only ACLs are\nbeing requested.  This results in a significant performance improvement\nas we can avoid querying for further information on these objects when\nwe don't need to.\n\nWhen limiting the components to dump for an extension, consider what\ncomponents have been requested.  Initially, we incorrectly hard-coded\nthe components of the extension objects to dump, which would mean that\nwe wouldn't dump some components even with they were asked for and in\nother cases we would dump components which weren't requested.\n\nCorrect defaultACLs to use 'dump_contains' instead of 'dump'.  The\ndefaultACL is considered a member of the namespace and should be\ndumped based on the same set of components that the other objects in\nthe schema are, not based on what we're dumping for the namespace\nitself (which might not include ACLs, if the namespace has just the\ndefault or initial ACL).\n\nUse DUMP_COMPONENT_ACL for from-initdb objects, to allow users to\nchange their ACLs, should they wish to.  This just extends what we\nare doing for the pg_catalog namespace to objects which are not\nmembers of namespaces.\n\nDue to column ACLs being treated a bit differently from other ACLs\n(they are actually reset to NULL when all privileges are revoked),\nadjust the query which gathers column-level ACLs to consider all of\nthe ACL-relevant columns.","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/5d589993cad212f7d556d52cc1e42fe18f65b057"},{"sha":"e1b120a8cbb0f39a79926fd173f33e57202cdfa0","author":{"email":"d3eaa418a359156a10c6383b2e3a44959960ecf6@snowman.net","name":"Stephen Frost"},"message":"Only issue LOCK TABLE commands when necessary\n\nReviewing the cases where we need to LOCK a given table during a dump,\nit was pointed out by Tom that we really don't need to LOCK a table if\nwe are only looking to dump the ACL for it, or certain other\ncomponents.  After reviewing the queries run for all of the component\npieces, a list of components were determined to not require LOCK'ing\nof the table.\n\nThis implements a check to avoid LOCK'ing those tables.\n\nInitial complaint from Rushabh Lathia, discussed with Robert and Tom,\nthe patch is mine.","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/e1b120a8cbb0f39a79926fd173f33e57202cdfa0"},{"sha":"6bd356c33a3cf3a49313dc8638ea4bb066c4cf37","author":{"email":"d3eaa418a359156a10c6383b2e3a44959960ecf6@snowman.net","name":"Stephen Frost"},"message":"Add TAP tests for pg_dump\n\nThis TAP test suite will create a new cluster, populate it based on\nthe 'create_sql' values in the '%tests' hash, run all of the runs\ndefined in the '%pgdump_runs' hash, and then for each test in the\n'%tests' hash, compare each run's output the the regular expression\ndefined for the test under the 'like' and 'unlike' functions, as\nappropriate.\n\nWhile this test suite covers a fair bit of ground (67% of pg_dump.c\nand quite a bit of the other files in src/bin/pg_dump), there is\nstill quite a bit which remains to be added to provide better code\ncoverage.  Still, this is quite a bit better than we had, and has\nfound a few bugs already (note that the CREATE TRANSFORM test is\ncommented out, as it is currently failing).\n\nIdea for using the TAP system from Tom, though all of the code is mine.","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/6bd356c33a3cf3a49313dc8638ea4bb066c4cf37"},{"sha":"a89505fd21da337b81172871d8f65d9a4fa22a8b","author":{"email":"d3eaa418a359156a10c6383b2e3a44959960ecf6@snowman.net","name":"Stephen Frost"},"message":"Remove various special checks around default roles\n\nDefault roles really should be like regular roles, for the most part.\nThis removes a number of checks that were trying to make default roles\nextra special by not allowing them to be used as regular roles.\n\nWe still prevent users from creating roles in the \"pg_\" namespace or\nfrom altering roles which exist in that namespace via ALTER ROLE, as\nwe can't preserve such changes, but otherwise the roles are very much\nlike regular roles.\n\nBased on discussion with Robert and Tom.","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/a89505fd21da337b81172871d8f65d9a4fa22a8b"}]}