{"push_id":2847364308,"size":3,"distinct_size":1,"ref":"refs/heads/commitfest/19/1605","head":"500a9995127bfffb34cb0cbc6e0daa698440fd8a","before":"f35b580cff939d2f7180f97d8019558a085e74c5","commits":[{"sha":"4ddd8f5f55a0a1967fc787e42182745ca1e3a995","author":{"name":"Tomas Vondra","email":"07d6043e15c7eaaf8513ba9a264e5412dbd73bf7@postgresql.org"},"message":"Fix memory leak in TRUNCATE decoding\n\nWhen decoding a TRUNCATE record, the relids array was being allocated in\nthe main ReorderBuffer memory context, but not released with the change\nresulting in a memory leak.\n\nThe array was also ignored when serializing/deserializing the change,\nassuming all the information is stored in the change itself.  So when\nspilling the change to disk, we've only we have serialized only the\npointer to the relids array.  Thanks to never releasing the array,\nthe pointer however remained valid even after loading the change back\nto memory, preventing an actual crash.\n\nThis fixes both the memory leak and (de)serialization.  The relids array\nis still allocated in the main ReorderBuffer memory context (none of the\nexisting ones seems like a good match, and adding an extra context seems\nlike an overkill).  The allocation is wrapped in a new ReorderBuffer API\nfunctions, to keep the details within reorderbuffer.c, just like the\nother ReorderBufferGet methods do.\n\nAuthor: Tomas Vondra\nDiscussion: https://www.postgresql.org/message-id/flat/66175a41-9342-2845-652f-1bd4c3ee50aa%402ndquadrant.com\nBackpatch: 11, where decoding of TRUNCATE was introduced","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/4ddd8f5f55a0a1967fc787e42182745ca1e3a995"},{"sha":"c076f3d74af6e4836206142446bdcc2f93e149d6","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"Remove pg_constraint.conincluding\n\nThis column was added in commit 8224de4f42cc (\"Indexes with INCLUDE\ncolumns and their support in B-tree\") to ease writing the ruleutils.c\nsupporting code for that feature, but it turns out to be unnecessary --\nwe can do the same thing with just one more syscache lookup.\n\nEven the documentation for the new column being removed in this commit\nis awkward.\n\nDiscussion: https://postgr.es/m/20180902165018.33otxftp3olgtu4t@alvherre.pgsql","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/c076f3d74af6e4836206142446bdcc2f93e149d6"},{"sha":"500a9995127bfffb34cb0cbc6e0daa698440fd8a","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 19/1605] Allow granting of permission to REFRESH MATERIALIZED VIEW, CLUSTER, and REINDEX\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, and also periodically to check for bitrot caused by changes\non the master branch.\n\nCommitfest entry: https://commitfest.postgresql.org/19/1605\nPatch(es): https://www.postgresql.org/message-id/CAMsGm5d3wKaM2ZHV-ZdE_xBsMGOcFqY-BiyJretS0Pc582tr=Q@mail.gmail.com\nAuthor(s): Isaac Morland","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/500a9995127bfffb34cb0cbc6e0daa698440fd8a"}]}
{"actor":{"display_login":"postgresql-cfbot"}}