{"push_id":1289296114,"size":1,"distinct_size":1,"ref":"refs/heads/REL9_6_STABLE","head":"31eb14504de311c98db2d1306ac61427bcdad863","before":"a88cee90fdfb2c125d56cb08164ca9a9ca39a75d","commits":[{"sha":"31eb14504de311c98db2d1306ac61427bcdad863","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Allow pg_dump to dump non-extension members of an extension-owned schema.\n\nPreviously, if a schema was created by an extension, a normal pg_dump run\n(not --binary-upgrade) would summarily skip every object in that schema.\nIn a case where an extension creates a schema and then users create other\nobjects within that schema, this does the wrong thing: we want pg_dump\nto skip the schema but still create the non-extension-owned objects.\n\nThere's no easy way to fix this pre-9.6, because in earlier versions the\n\"dump\" status for a schema is just a bool and there's no way to distinguish\n\"dump me\" from \"dump my members\".  However, as of 9.6 we do have enough\nstate to represent that, so this is a simple correction of the logic in\nselectDumpableNamespace.\n\nIn passing, make some cosmetic fixes in nearby code.\n\nMartín Marqués, reviewed by Michael Paquier\n\nDiscussion: <99581032-71de-6466-c325-069861f1947d@2ndquadrant.com>","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/31eb14504de311c98db2d1306ac61427bcdad863"}]}
{"actor":{"display_login":"postgres-mirror"}}