payload: {"push_id":4292184306,"size":4,"distinct_size":1,"ref":"refs/heads/commitfest/25/2213","head":"fb4146400f8389667872979e79ca2620d353866b","before":"4a4bab596b069ba60d9d9f2f3f7c46699f366813","commits":[{"sha":"2110f716965fe1ac5af83380aa108541b1457e0d","author":{"name":"Peter Geoghegan","email":"96dd8d96902e9c5af3b96b1eaa9c80cbc615d290@bowt.ie"},"message":"nbtree: Tweak _bt_pgaddtup() comments.\n\nMake it clear that _bt_pgaddtup() truncates the first data item on an\ninternal page because its key is supposed to be treated as minus\ninfinity within _bt_compare().","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/2110f716965fe1ac5af83380aa108541b1457e0d"},{"sha":"cec2edfa7859279f36d2374770ca920c59c73dd8","author":{"name":"Amit Kapila","email":"4c828daf437d3cc4e3dadceacc8c2924836485c1@postgresql.org"},"message":"Add logical_decoding_work_mem to limit ReorderBuffer memory usage.\n\nInstead of deciding to serialize a transaction merely based on the\nnumber of changes in that xact (toplevel or subxact), this makes\nthe decisions based on amount of memory consumed by the changes.\n\nThe memory limit is defined by a new logical_decoding_work_mem GUC,\nso for example we can do this\n\n    SET logical_decoding_work_mem = '128kB'\n\nto reduce the memory usage of walsenders or set the higher value to\nreduce disk writes. The minimum value is 64kB.\n\nWhen adding a change to a transaction, we account for the size in\ntwo places. Firstly, in the ReorderBuffer, which is then used to\ndecide if we reached the total memory limit. And secondly in the\ntransaction the change belongs to, so that we can pick the largest\ntransaction to evict (and serialize to disk).\n\nWe still use max_changes_in_memory when loading changes serialized\nto disk. The trouble is we can't use the memory limit directly as\nthere might be multiple subxact serialized, we need to read all of\nthem but we don't know how many are there (and which subxact to\nread first).\n\nWe do not serialize the ReorderBufferTXN entries, so if there is a\ntransaction with many subxacts, most memory may be in this type of\nobjects. Those records are not included in the memory accounting.\n\nWe also do not account for INTERNAL_TUPLECID changes, which are\nkept in a separate list and not evicted from memory. Transactions\nwith many CTID changes may consume significant amounts of memory,\nbut we can't really do much about that.\n\nThe current eviction algorithm is very simple - the transaction is\npicked merely by size, while it might be useful to also consider age\n(LSN) of the changes for example. With the new Generational memory\nallocator, evicting the oldest changes would make it more likely\nthe memory gets actually pfreed.\n\nThe logical_decoding_work_mem can be set in postgresql.conf, in which\ncase it serves as the default for all publishers on that instance.\n\nAuthor: Tomas Vondra, with changes by Dilip Kumar and Amit Kapila\nReviewed-by: Dilip Kumar and Amit Kapila\nTested-By: Vignesh C\nDiscussion: https://postgr.es/m/688b0b7f-2f6c-d827-c27b-216a8e3ea700@2ndquadrant.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/cec2edfa7859279f36d2374770ca920c59c73dd8"},{"sha":"7f338369ca624ca6c2e4f579623274c88d325bce","author":{"name":"Thomas Munro","email":"1ff054ef0838bf068a4b7c40eef026e560a37025@postgresql.org"},"message":"Allow invisible PROMPT2 in psql.\n\nKeep track of the visible width of PROMPT1, and provide %w as a way\nfor PROMPT2 to generate the same number of spaces.\n\nAuthor: Thomas Munro, with ideas from others\nReviewed-by: Tom Lane (earlier version)\nDiscussion: https://postgr.es/m/CA%2BhUKG%2BzGd7RigjWbxwhzGW59gUpf76ydQECeGdEdodH6nd__A%40mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/7f338369ca624ca6c2e4f579623274c88d325bce"},{"sha":"fb4146400f8389667872979e79ca2620d353866b","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 25/2213] Add FOREIGN to ALTER TABLE in pg_dump when the target is a foreign table\n\nThis commit was automatically generated by a robot at cfbot.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/25/2213\nPatch(es): https://www.postgresql.org/message-id/LEXPR01MB107277A337B67F5C6B68E6AAE7860@LEXPR01MB1072.DEUPRD01.PROD.OUTLOOK.DE\nAuthor(s): Luis M Carril","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/fb4146400f8389667872979e79ca2620d353866b"}]}
other: {"actor":{"display_login":"postgresql-cfbot"}}