{"push_id":2921303197,"size":3,"distinct_size":1,"ref":"refs/heads/commitfest/19/1667","head":"2488ae7d6797893757154d8c695d39078f203c5f","before":"25bbb8996f12c461bac71b88aad3269fa4465e2a","commits":[{"sha":"fdba460a26af919c0b366755d119f384706e670a","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Create an RTE field to record the query's lock mode for each relation.\n\nAdd RangeTblEntry.rellockmode, which records the appropriate lock mode for\neach RTE_RELATION rangetable entry (either AccessShareLock, RowShareLock,\nor RowExclusiveLock depending on the RTE's role in the query).\n\nThis patch creates the field and makes all creators of RTE nodes fill it\nin reasonably, but for the moment nothing much is done with it.  The plan\nis to replace assorted post-parser logic that re-determines the right\nlockmode to use with simple uses of rte->rellockmode.  For now, just add\nAsserts in each of those places that the rellockmode matches what they are\ncomputing today.  (In some cases the match isn't perfect, so the Asserts\nare weaker than you might expect; but this seems OK, as per discussion.)\n\nThis passes check-world for me, but it seems worth pushing in this state\nto see if the buildfarm finds any problems in cases I failed to test.\n\ncatversion bump due to change of stored rules.\n\nAmit Langote, reviewed by David Rowley and Jesper Pedersen,\nand whacked around a bit more by me\n\nDiscussion: https://postgr.es/m/468c85d9-540e-66a2-1dde-fec2b741e688@lab.ntt.co.jp","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/fdba460a26af919c0b366755d119f384706e670a"},{"sha":"a6949ca34d3aca018870815cf6cb690024aeea04","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"doc: Clarify CREATE TABLESPACE documentation\n\nBe more specific about when and how to create the directory and what\npermissions it should have.\n\nDiscussion: https://www.postgresql.org/message-id/flat/5ca60e1a-26f9-89fd-e912-021dd2b8afe2%40gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/a6949ca34d3aca018870815cf6cb690024aeea04"},{"sha":"2488ae7d6797893757154d8c695d39078f203c5f","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 19/1667] cursors with prepared statements\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/1667\nPatch(es): https://www.postgresql.org/message-id/d5c1859d-40a6-07c0-eba9-32e0d3a22cdc@iki.fi\nAuthor(s): Peter Eisentraut","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/2488ae7d6797893757154d8c695d39078f203c5f"}]}
{"actor":{"display_login":"postgresql-cfbot"}}