{"push_id":705656995,"size":141,"distinct_size":1,"ref":"refs/heads/pg_database_add_datcreated_column","head":"a5e189eb8f332fa4a63de07837e0c5eec67f5d11","before":"7cf8a8d2c5d9ce5cee353b184bb73712783036d8","commits":[{"sha":"6d1733fa90a3f8037c7c815ed6ab4d97c295e525","author":{"email":"1f6acd02e97f7332f0e624e7be5170a1e771cb87@postgresql.org","name":"Fujii Masao"},"message":"Minor enhancement of readability of ALTER TABLE syntax in the doc.\n\nFabrízio Mello","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/6d1733fa90a3f8037c7c815ed6ab4d97c295e525"},{"sha":"5302760a50332a684e35b9865ff47ff5fd4970c2","author":{"email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@dunslane.net","name":"Andrew Dunstan"},"message":"Unpack jbvBinary objects passed to pushJsonbValue\n\npushJsonbValue was accepting jbvBinary objects passed as WJB_ELEM or\nWJB_VALUE data. While this succeeded, when those objects were later\nencountered in attempting to convert the result to Jsonb, errors\noccurred. With this change we ghuarantee that a JSonbValue constructed\nfrom calls to pushJsonbValue does not contain any jbvBinary objects.\nThis cures a problem observed with jsonb_delete.\n\nThis means callers of pushJsonbValue no longer need to perform this\nunpacking themselves. A subsequent patch will perform some cleanup in\nthat area.\n\nThe error was not triggered by any 9.4 code, but this is a publicly\nvisible routine, and so the error could be exercised by third party\ncode, therefore backpatch to 9.4.\n\nBug report from Peter Geoghegan, fix by me.","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/5302760a50332a684e35b9865ff47ff5fd4970c2"},{"sha":"49ad32d5d99cb4a79bf648c0b7f9eca19b54cf1d","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Fix recently-introduced crash in array_contain_compare().\n\nSilly oversight in commit 1dc5ebc9077ab742079ce5dac9a6664248d42916:\nwhen array2 is an expanded array, it might have array2->xpn.dnulls equal\nto NULL, indicating the array is known null-free.  The code wasn't\nexpecting that, because it formerly always used deconstruct_array() which\nalways delivers a nulls array.\n\nPer bug #13334 from Regina Obe.","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/49ad32d5d99cb4a79bf648c0b7f9eca19b54cf1d"},{"sha":"631d7490074cdaef8026db57a5f2772b8730f600","author":{"email":"883768b6dd2c42aea0031b24be8a2da40fef4b64@anarazel.de","name":"Andres Freund"},"message":"Remove the new UPSERT command tag and use INSERT instead.\n\nPreviously, INSERT with ON CONFLICT DO UPDATE specified used a new\ncommand tag -- UPSERT.  It was introduced out of concern that INSERT as\na command tag would be a misrepresentation for ON CONFLICT DO UPDATE, as\nsome affected rows may actually have been updated.\n\nAlvaro Herrera noticed that the implementation of that new command tag\nwas incomplete; in subsequent discussion we concluded that having it\ndoesn't provide benefits that are in line with the compatibility breaks\nit requires.\n\nCatversion bump due to the removal of PlannedStmt->isUpsert.\n\nAuthor: Peter Geoghegan\nDiscussion: 20150520215816.GI5885@postgresql.org","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/631d7490074cdaef8026db57a5f2772b8730f600"},{"sha":"284bef297733e553c73f1c858e0ce1532f754d18","author":{"email":"883768b6dd2c42aea0031b24be8a2da40fef4b64@anarazel.de","name":"Andres Freund"},"message":"Fix yet another bug in ON CONFLICT rule deparsing.\n\nExpand testing of rule deparsing a good bit, it's evidently needed.\n\nAuthor: Peter Geoghegan, Andres Freund\nDiscussion: CAM3SWZQmXxZhQC32QVEOTYfNXJBJ_Q2SDENL7BV14Cq-zL0FLg@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/284bef297733e553c73f1c858e0ce1532f754d18"},{"sha":"821b821a2421beaa58225ff000833df69fb962c5","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Still more fixes for lossy-GiST-distance-functions patch.\n\nFix confusion in documentation, substantial memory leakage if float8 or\nfloat4 are pass-by-reference, and assorted comments that were obsoleted\nby commit 98edd617f3b62a02cb2df9b418fcc4ece45c7ec0.","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/821b821a2421beaa58225ff000833df69fb962c5"},{"sha":"72809480d658fbc0654239b2f089991c077c676a","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Fix incorrect snprintf() limit.\n\nTypo in commit 7cbee7c0a.  No practical effect since the buffer should\nnever actually be overrun, but various compilers and static analyzers will\nwhine about it.\n\nPetr Jelinek","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/72809480d658fbc0654239b2f089991c077c676a"},{"sha":"f84c8601d604811a530dadb53ddb52f08639e72b","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Add error check for lossy distance functions in index-only scans.\n\nMaybe we should actually support this, but for the moment let's just\nthrow an error if the opclass tries it.","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/f84c8601d604811a530dadb53ddb52f08639e72b"},{"sha":"58affdfb88a7705df477f0cfc0710bf638ccd3e9","author":{"email":"9ae9c44b775ee9b29f4f502415e02e61a9b1a6a0@momjian.us","name":"Bruce Momjian"},"message":"Improve pgindent instructions regarding Perl backup files","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/58affdfb88a7705df477f0cfc0710bf638ccd3e9"},{"sha":"225892552bd3052982d2b97b749e5945ea71facc","author":{"email":"9ae9c44b775ee9b29f4f502415e02e61a9b1a6a0@momjian.us","name":"Bruce Momjian"},"message":"Update typedef file in preparation for pgindent run","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/225892552bd3052982d2b97b749e5945ea71facc"},{"sha":"807b9e0dff663c5da875af7907a5106c0ff90673","author":{"email":"9ae9c44b775ee9b29f4f502415e02e61a9b1a6a0@momjian.us","name":"Bruce Momjian"},"message":"pgindent run for 9.5","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/807b9e0dff663c5da875af7907a5106c0ff90673"},{"sha":"91e79260f636ab4d5a43910b6a38bc75651ad14c","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Remove no-longer-required function declarations.\n\nRemove a bunch of \"extern Datum foo(PG_FUNCTION_ARGS);\" declarations that\nare no longer needed now that PG_FUNCTION_INFO_V1(foo) provides that.\n\nSome of these were evidently missed in commit e7128e8dbb305059, but others\nwere cargo-culted in in code added since then.  Possibly that can be blamed\nin part on the fact that we'd not fixed relevant documentation examples,\nwhich I've now done.","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/91e79260f636ab4d5a43910b6a38bc75651ad14c"},{"sha":"23116d5437d0e8d077e7fd5391f5fa0fc781b7d2","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Add a bit more commentary about regex's colormap tree data structure.\n\nPer an off-list question from Piotr Stefaniak.","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/23116d5437d0e8d077e7fd5391f5fa0fc781b7d2"},{"sha":"17b48a1a9f87f7479d38dcc78a27c23f1f8124f8","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Rename pg_shdepend.c's typedef \"objectType\" to SharedDependencyObjectType.\n\nThe name objectType is widely used as a field name, and it's pure luck that\nthis conflict has not caused pgindent to go crazy before.  It messed up\npg_audit.c pretty good though.  Since pg_shdepend.c doesn't export this\ntypedef and only uses it in three places, changing that seems saner than\nchanging the field usages.\n\nBack-patch because we're contemplating using the union of all branch\ntypedefs for future pgindent runs, so this won't fix anything if it\nstays the same in back branches.","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/17b48a1a9f87f7479d38dcc78a27c23f1f8124f8"},{"sha":"2aa0476dc38f7e510b8cde627e83b4c76fa05d61","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Manual cleanup of pgindent results.\n\nFix some places where pgindent did silly stuff, often because project\nstyle wasn't followed to begin with.  (I've not touched the atomics\nheaders, though.)","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/2aa0476dc38f7e510b8cde627e83b4c76fa05d61"},{"sha":"befa3e648ce018d84cd2a0df701927c56fe3da4e","author":{"email":"9ae9c44b775ee9b29f4f502415e02e61a9b1a6a0@momjian.us","name":"Bruce Momjian"},"message":"Revert 9.5 pgindent changes to atomics directory files\n\nThis is because there are many __asm__ blocks there that pgindent messes\nup.  Also configure pgindent to skip that directory in the future.","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/befa3e648ce018d84cd2a0df701927c56fe3da4e"},{"sha":"266b6984cd7391e42770ca3a9922a9e8b1d4d7d3","author":{"email":"9ae9c44b775ee9b29f4f502415e02e61a9b1a6a0@momjian.us","name":"Bruce Momjian"},"message":"pgindent:  more doc updates for skipping __asm__ files","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/266b6984cd7391e42770ca3a9922a9e8b1d4d7d3"},{"sha":"12e6c5a6cae1e34da2d320390993010b6e15ba9e","author":{"email":"ac1e0af1ee8efe15f889b38482e897ff7d0f0432@iki.fi","name":"Heikki Linnakangas"},"message":"Fix rescan of IndexScan node with the new lossy GiST distance functions.\n\nMust reset the \"reached end\" flag and reorder queue at rescan.\n\nPer report from Regina Obe, bug #13349","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/12e6c5a6cae1e34da2d320390993010b6e15ba9e"},{"sha":"8339e70da6682059f7ab40f0c0b0dfcdcb78761d","author":{"email":"9ae9c44b775ee9b29f4f502415e02e61a9b1a6a0@momjian.us","name":"Bruce Momjian"},"message":"pgindent:  fix typo\n\nReport by Michael Paquier","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/8339e70da6682059f7ab40f0c0b0dfcdcb78761d"},{"sha":"6739aa298b5e3260481a2d5723a75b057d6119c6","author":{"email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@dunslane.net","name":"Andrew Dunstan"},"message":"Clean up and simplify jsonb_concat code.\n\nSome of this is made possible by commit\n9b74f32cdbff8b9be47fc69164eae552050509ff which lets pushJsonbValue\nhandle binary Jsonb values, meaning that clients no longer have to, and\nsome is just doing things in simpler and more straightforward ways.","distinct":false,"url":"https://api.github.com/repos/fabriziomello/postgres/commits/6739aa298b5e3260481a2d5723a75b057d6119c6"}]}