{"push_id":2410391493,"size":3,"distinct_size":1,"ref":"refs/heads/commitfest/17/1494","head":"89793d6dd93e929610c39921fd491d8336b8332a","before":"fa32b186547cec926b0592ff4f60dc338c6d131e","commits":[{"sha":"013c0baaddd9df7e1f940184a8ab8e478214b46c","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Doc: explicitly point out that enum values can't be dropped.\n\nThis was not stated in so many words anywhere.  Document it to make\nclear that it's a design limitation and not just an oversight or\ndocumentation omission.\n\nDiscussion: https://postgr.es/m/152089733343.1222.6927268289645380498@wrigleys.postgresql.org","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/013c0baaddd9df7e1f940184a8ab8e478214b46c"},{"sha":"9e17bdb8a525ff89c4535cd153dc0f2fa813ea59","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix query-lifespan memory leakage in repeatedly executed hash joins.\n\nExecHashTableCreate allocated some memory that wasn't freed by\nExecHashTableDestroy, specifically the per-hash-key function information.\nThat's not a huge amount of data, but if one runs a query that repeats\na hash join enough times, it builds up.  Fix by arranging for the data\nin question to be kept in the hashtable's hashCxt instead of leaving it\n\"loose\" in the query-lifespan executor context.  (This ensures that we'll\nalso clean up anything that the hash functions allocate in fn_mcxt.)\n\nPer report from Amit Khandekar.  It's been like this forever, so back-patch\nto all supported branches.\n\nDiscussion: https://postgr.es/m/CAJ3gD9cFofAWGvcxLOxDHC=B0hjtW8yGmUsF2hdGh97CM38=7g@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/9e17bdb8a525ff89c4535cd153dc0f2fa813ea59"},{"sha":"89793d6dd93e929610c39921fd491d8336b8332a","author":{"name":"Commitfest Bot","email":"aab6a594935fe5db0d690bc154b19f642bfbe9d7@cputube.org"},"message":"[CF 17/1494] Support optional message in backend cancellation/termination\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/17/1494\nPatch(es): https://www.postgresql.org/message-id/6748C86B-30D3-44DC-848E-562DB2605874%40yesql.se\nAuthor(s): Daniel Gustafsson","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/89793d6dd93e929610c39921fd491d8336b8332a"}]}
{"actor":{"display_login":"postgresql-cfbot"}}