{"push_id":2497992886,"size":5,"distinct_size":1,"ref":"refs/heads/commitfest/18/1528","head":"3a589892fcf65f02500cb055278a3f85d7c652b0","before":"ed61fe5f4c8b815b5703d07c5f0b67e9536e96d5","commits":[{"sha":"075aade4361b9f973172b925ddfb908a012b5796","author":{"name":"Teodor Sigaev","email":"231337598724646720571a00c656f975fff6a8f2@sigaev.ru"},"message":"Adjust INCLUDE index truncation comments and code.\n\nAdd several assertions that ensure that we're dealing with a pivot tuple\nwithout non-key attributes where that's expected.  Also, remove the\nassertion within _bt_isequal(), restoring the v10 function signature.  A\nsimilar check will be performed for the page highkey within\n_bt_moveright() in most cases.  Also avoid dropping all objects within\nregression tests, to increase pg_dump test coverage for INCLUDE indexes.\n\nRather than using infrastructure that's generally intended to be used\nwith reference counted heap tuple descriptors during truncation, use the\nsame function that was introduced to store flat TupleDescs in shared\nmemory (we use a temp palloc'd buffer).  This isn't strictly necessary,\nbut seems more future-proof than the old approach.  It also lets us\navoid including rel.h within indextuple.c, which was arguably a\nmodularity violation.  Also, we now call index_deform_tuple() with the\ntruncated TupleDesc, not the source TupleDesc, since that's more robust,\nand saves a few cycles.\n\nIn passing, fix a memory leak by pfree'ing truncated pivot tuple memory\nduring CREATE INDEX.  Also pfree during a page split, just to be\nconsistent.\n\nRefactor _bt_check_natts() to be more readable.\n\nAuthor: Peter Geoghegan with some editorization by me\nReviewed by: Alexander Korotkov, Teodor Sigaev\nDiscussion: https://www.postgresql.org/message-id/CAH2-Wz%3DkCWuXeMrBCopC-tFs3FbiVxQNjjgNKdG2sHxZ5k2y3w%40mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/075aade4361b9f973172b925ddfb908a012b5796"},{"sha":"3d927961ae1232487796bebb254d92fb6d0d1e03","author":{"name":"Teodor Sigaev","email":"231337598724646720571a00c656f975fff6a8f2@sigaev.ru"},"message":"Handle XLOG_BTREE_META_CLEANUP in btree_desc() and btree_identify()\n\nNew WAL record XLOG_BTREE_META_CLEANUP introduced in 857f9c36 has no handling\nin btree_desc() and btree_identify().  This patch implements corresponding\nhandling.\n\nAlexander Korotkov","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/3d927961ae1232487796bebb254d92fb6d0d1e03"},{"sha":"f97f0c921ae56bb16e466f3c9d6c504f4a96a539","author":{"name":"Teodor Sigaev","email":"231337598724646720571a00c656f975fff6a8f2@sigaev.ru"},"message":"Adjust _bt_insertonpg() comments\n\nRemove an obsolete reference to the 'afteritem' argument, which was\nremoved by commit bc292937.  Add a comment that clarifies how\n_bt_insertonpg() indirectly handles the insertion of high key items.\n\nAuthor: Peter Geoghegan","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/f97f0c921ae56bb16e466f3c9d6c504f4a96a539"},{"sha":"ff4943042f9761fb4e84432da563f43eb3559a3b","author":{"name":"Teodor Sigaev","email":"231337598724646720571a00c656f975fff6a8f2@sigaev.ru"},"message":"Fix datatype for number of heap tuples during last cleanup\n\nIt appears that new fields introduced in 857f9c36 have inconsistent datatypes:\nBTMetaPageData.btm_last_cleanup_num_heap_tuples is of float4 type,\nwhile xl_btree_metadata.last_cleanup_num_heap_tuples is of double type.\nIndexVacuumInfo.num_heap_tuples, which is a source of values for\nboth former fields is of double type.  So, make both those fields in\nBTMetaPageData and xl_btree_metadata use float8 type in order to match the\nprecision of the source.  That shouldn't be double type, because we always\nuse types with explicit width in WAL.\n\nPatch introduces incompatibility of on-disk format since 857f9c36 commit, but\nthat versions never was released, so just bump catalog version to avoid\npossible confusion.\n\nAuthor: Alexander Korortkov","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/ff4943042f9761fb4e84432da563f43eb3559a3b"},{"sha":"3a589892fcf65f02500cb055278a3f85d7c652b0","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 18/1528] pgbench - test whether a variable exists\n\nThis commit was automatically generated by cfbot at commitfest.cputube.org.\nIt is based on patches submitted to the PostgreSQL mailing lists and\nregistered in the PostgreSQL Commitfest application.\n\nThis branch will be overwritten each time a new patch version is posted to\nthe email thread or the master branch changes.\n\nCommitfest entry: https://commitfest.postgresql.org/18/1528\nPatch(es): https://www.postgresql.org/message-id/alpine.DEB.2.20.1803271408090.28541%40lancre\nAuthor(s): Fabien Coelho","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/3a589892fcf65f02500cb055278a3f85d7c652b0"}]}
{"actor":{"display_login":"postgresql-cfbot"}}