{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":927442,"defaultBranch":"master","name":"postgres","ownerLogin":"postgres","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2010-09-21T11:35:45.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/177543?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1716410218.0","currentOid":""},"activityList":{"items":[{"before":"3a2cc5a5b99ab04b9dc7e5f6c46b564739b5eb1b","after":"b4e909082fa114d5934ca622b225d2352ec639fa","ref":"refs/heads/REL_16_STABLE","pushedAt":"2024-06-04T10:54:54.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Fix PL/pgSQL's handling of integer ranges containing underscores.\n\nCommit faff8f8e47 allowed integer literals to contain underscores, but\nfailed to update the lexer's \"numericfail\" rule. As a result, a\ndecimal integer literal containing underscores would fail to parse, if\nused in an integer range with no whitespace after the first number,\nsuch as \"1_001..1_003\" in a PL/pgSQL FOR loop.\n\nFix and backpatch to v16, where support for underscores in integer\nliterals was added.\n\nReport and patch by Erik Wienhold.\n\nDiscussion: https://postgr.es/m/808ce947-46ec-4628-85fa-3dd600b2c154%40ewie.name","shortMessageHtmlLink":"Fix PL/pgSQL's handling of integer ranges containing underscores."}},{"before":"5c5bccef211cfc98e0d6c4bc1af40a33c8ac2488","after":"cd2624fd97b0c36b68da278abc5362647f69b07d","ref":"refs/heads/master","pushedAt":"2024-06-04T10:54:54.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Fix PL/pgSQL's handling of integer ranges containing underscores.\n\nCommit faff8f8e47 allowed integer literals to contain underscores, but\nfailed to update the lexer's \"numericfail\" rule. As a result, a\ndecimal integer literal containing underscores would fail to parse, if\nused in an integer range with no whitespace after the first number,\nsuch as \"1_001..1_003\" in a PL/pgSQL FOR loop.\n\nFix and backpatch to v16, where support for underscores in integer\nliterals was added.\n\nReport and patch by Erik Wienhold.\n\nDiscussion: https://postgr.es/m/808ce947-46ec-4628-85fa-3dd600b2c154%40ewie.name","shortMessageHtmlLink":"Fix PL/pgSQL's handling of integer ranges containing underscores."}},{"before":"83fc61ccfaf38aebe73eacdfc712106797d75b39","after":"5c5bccef211cfc98e0d6c4bc1af40a33c8ac2488","ref":"refs/heads/master","pushedAt":"2024-06-04T08:34:15.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Fix another couple of outdated comments for MERGE RETURNING.\n\nOversights in c649fa24a4 which added RETURNING support to MERGE.\n\nDiscussion: https://postgr.es/m/CAApHDvpqp6vtUzG-_josUEiBGyqnrnVxJ-VdF+hJLXjHdHzsyQ@mail.gmail.com","shortMessageHtmlLink":"Fix another couple of outdated comments for MERGE RETURNING."}},{"before":"65b8c401af0a1d98ad34e60f8667e149796f8889","after":"3a2cc5a5b99ab04b9dc7e5f6c46b564739b5eb1b","ref":"refs/heads/REL_16_STABLE","pushedAt":"2024-06-04T02:42:40.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"ci: windows: Use the same image for VS and MinGW tasks\n\nThe VS and MinGW Windows images have been merged, to reduce the space needed\nfor images. Before 98811323c8e the split helped boot performance, but now that\nwe are using VMs that doesn't appear to be the case anymore.\n\nAuthor: Nazir Bilal Yavuz <byavuz81@gmail.com>\nDiscussion: https://postgr.es/m/CAN55FZ2kWYjPd7uUC5QswrB3tfVJDiURqC%2BMGM6a3oeev%3DVgOA%40mail.gmail.com\nBackpatch: 15-, where CI was added","shortMessageHtmlLink":"ci: windows: Use the same image for VS and MinGW tasks"}},{"before":"f1884f57570ca73005d7a5b55eddd7af5c7067f7","after":"6b52e2298d8529eab777eaca339da3b04c862f9c","ref":"refs/heads/REL_15_STABLE","pushedAt":"2024-06-04T02:42:40.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"ci: windows: Use the same image for VS and MinGW tasks\n\nThe VS and MinGW Windows images have been merged, to reduce the space needed\nfor images. Before 98811323c8e the split helped boot performance, but now that\nwe are using VMs that doesn't appear to be the case anymore.\n\nAuthor: Nazir Bilal Yavuz <byavuz81@gmail.com>\nDiscussion: https://postgr.es/m/CAN55FZ2kWYjPd7uUC5QswrB3tfVJDiURqC%2BMGM6a3oeev%3DVgOA%40mail.gmail.com\nBackpatch: 15-, where CI was added","shortMessageHtmlLink":"ci: windows: Use the same image for VS and MinGW tasks"}},{"before":"f04d1c1db01199f02b0914a7ca2962c531935717","after":"83fc61ccfaf38aebe73eacdfc712106797d75b39","ref":"refs/heads/master","pushedAt":"2024-06-04T02:42:40.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"ci: windows: Use the same image for VS and MinGW tasks\n\nThe VS and MinGW Windows images have been merged, to reduce the space needed\nfor images. Before 98811323c8e the split helped boot performance, but now that\nwe are using VMs that doesn't appear to be the case anymore.\n\nAuthor: Nazir Bilal Yavuz <byavuz81@gmail.com>\nDiscussion: https://postgr.es/m/CAN55FZ2kWYjPd7uUC5QswrB3tfVJDiURqC%2BMGM6a3oeev%3DVgOA%40mail.gmail.com\nBackpatch: 15-, where CI was added","shortMessageHtmlLink":"ci: windows: Use the same image for VS and MinGW tasks"}},{"before":"4ebe51a5fbc3e08861db85fe3868c31c6bc8ed59","after":"f04d1c1db01199f02b0914a7ca2962c531935717","ref":"refs/heads/master","pushedAt":"2024-06-03T22:17:01.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Improve assertion in mdwritev()\n\nThe assertion used at the beginning of mdwritev(), that is not enabled\nexcept by defining -DCHECK_WRITE_VS_EXTEND as mdnblocks() is costly,\nforgot about the total number of blocks to write at location specified\nby the caller.  The calculation is fixed to count for that, and uses\ncasts to uint64 to ensure a proper check should the number of blocks\noverflow.\n\nUsing a cast is a suggestion from Tom Lane.\n\nOversight in 4908c5872059.\n\nAuthor: Xing Guo\nDiscussion: https://postgr.es/m/CACpMh+BM-VgKeO7suPG-VHTtpzJ+zsbDPwVHu42PLp-iTk0z+A@mail.gmail.com","shortMessageHtmlLink":"Improve assertion in mdwritev()"}},{"before":"cd8f1c1207994c8b3d41c48a02fa40547ee48bea","after":"09d7caad32d8d6987964a85ff71d12f18f63f43f","ref":"refs/heads/REL_12_STABLE","pushedAt":"2024-06-03T17:12:26.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Fix documentation for System V semaphores.\n\nThe formulas for SEMMNI and SEMMNS do not include the archiver\nprocess, which was converted to an auxiliary process in v14, and\nthe WAL summarizer process, which was introduced in v17.  This\ncommit corrects these formulas and adds a missing reference to\nmax_wal_senders nearby.  Since this section of the documentation\ntends to be incorrect quite often, we should likely give up on\ndocumenting the exact formulas in favor of something less fragile,\nbut that is left as a future exercise.\n\nReported-by: Sami Imseih\nReviewed-by: Sami Imseih\nDiscussion: https://postgr.es/m/20240517164452.GA1914161%40nathanxps13\nBackpatch-through: 12","shortMessageHtmlLink":"Fix documentation for System V semaphores."}},{"before":"2e062b65539ea9f85cf591ffbc4cd2db30bf5f51","after":"1d5c5ae8e5557cfb974c290693802d8ebece25ac","ref":"refs/heads/REL_13_STABLE","pushedAt":"2024-06-03T17:12:26.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Fix documentation for System V semaphores.\n\nThe formulas for SEMMNI and SEMMNS do not include the archiver\nprocess, which was converted to an auxiliary process in v14, and\nthe WAL summarizer process, which was introduced in v17.  This\ncommit corrects these formulas and adds a missing reference to\nmax_wal_senders nearby.  Since this section of the documentation\ntends to be incorrect quite often, we should likely give up on\ndocumenting the exact formulas in favor of something less fragile,\nbut that is left as a future exercise.\n\nReported-by: Sami Imseih\nReviewed-by: Sami Imseih\nDiscussion: https://postgr.es/m/20240517164452.GA1914161%40nathanxps13\nBackpatch-through: 12","shortMessageHtmlLink":"Fix documentation for System V semaphores."}},{"before":"8fea1bd5411b793697a4c9087c403887e050c4ac","after":"4ebe51a5fbc3e08861db85fe3868c31c6bc8ed59","ref":"refs/heads/master","pushedAt":"2024-06-03T17:12:26.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Fix documentation for System V semaphores.\n\nThe formulas for SEMMNI and SEMMNS do not include the archiver\nprocess, which was converted to an auxiliary process in v14, and\nthe WAL summarizer process, which was introduced in v17.  This\ncommit corrects these formulas and adds a missing reference to\nmax_wal_senders nearby.  Since this section of the documentation\ntends to be incorrect quite often, we should likely give up on\ndocumenting the exact formulas in favor of something less fragile,\nbut that is left as a future exercise.\n\nReported-by: Sami Imseih\nReviewed-by: Sami Imseih\nDiscussion: https://postgr.es/m/20240517164452.GA1914161%40nathanxps13\nBackpatch-through: 12","shortMessageHtmlLink":"Fix documentation for System V semaphores."}},{"before":"338fb8714c6cfe30c567ecb79812ec3879bd117f","after":"65b8c401af0a1d98ad34e60f8667e149796f8889","ref":"refs/heads/REL_16_STABLE","pushedAt":"2024-06-03T17:12:26.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Fix documentation for System V semaphores.\n\nThe formulas for SEMMNI and SEMMNS do not include the archiver\nprocess, which was converted to an auxiliary process in v14, and\nthe WAL summarizer process, which was introduced in v17.  This\ncommit corrects these formulas and adds a missing reference to\nmax_wal_senders nearby.  Since this section of the documentation\ntends to be incorrect quite often, we should likely give up on\ndocumenting the exact formulas in favor of something less fragile,\nbut that is left as a future exercise.\n\nReported-by: Sami Imseih\nReviewed-by: Sami Imseih\nDiscussion: https://postgr.es/m/20240517164452.GA1914161%40nathanxps13\nBackpatch-through: 12","shortMessageHtmlLink":"Fix documentation for System V semaphores."}},{"before":"0795a35d13089c203f1b1ef523824c2fc22a6af9","after":"d0c11ea29846e66a49eecc62260d11709da3c73e","ref":"refs/heads/REL_14_STABLE","pushedAt":"2024-06-03T17:12:26.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Fix documentation for System V semaphores.\n\nThe formulas for SEMMNI and SEMMNS do not include the archiver\nprocess, which was converted to an auxiliary process in v14, and\nthe WAL summarizer process, which was introduced in v17.  This\ncommit corrects these formulas and adds a missing reference to\nmax_wal_senders nearby.  Since this section of the documentation\ntends to be incorrect quite often, we should likely give up on\ndocumenting the exact formulas in favor of something less fragile,\nbut that is left as a future exercise.\n\nReported-by: Sami Imseih\nReviewed-by: Sami Imseih\nDiscussion: https://postgr.es/m/20240517164452.GA1914161%40nathanxps13\nBackpatch-through: 12","shortMessageHtmlLink":"Fix documentation for System V semaphores."}},{"before":"8e16f81f3db4eb03ac2195e9e5527852047c14a0","after":"f1884f57570ca73005d7a5b55eddd7af5c7067f7","ref":"refs/heads/REL_15_STABLE","pushedAt":"2024-06-03T17:12:26.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Fix documentation for System V semaphores.\n\nThe formulas for SEMMNI and SEMMNS do not include the archiver\nprocess, which was converted to an auxiliary process in v14, and\nthe WAL summarizer process, which was introduced in v17.  This\ncommit corrects these formulas and adds a missing reference to\nmax_wal_senders nearby.  Since this section of the documentation\ntends to be incorrect quite often, we should likely give up on\ndocumenting the exact formulas in favor of something less fragile,\nbut that is left as a future exercise.\n\nReported-by: Sami Imseih\nReviewed-by: Sami Imseih\nDiscussion: https://postgr.es/m/20240517164452.GA1914161%40nathanxps13\nBackpatch-through: 12","shortMessageHtmlLink":"Fix documentation for System V semaphores."}},{"before":"4013a5ada25241ead6a3265d6edf9aadb654dc00","after":"8fea1bd5411b793697a4c9087c403887e050c4ac","ref":"refs/heads/master","pushedAt":"2024-05-28T04:21:44.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"doc PG 17 relnotes:  adjust IN wording\n\nReported-by: David Rowley\n\nDiscussion: https://postgr.es/m/CAApHDvqmW0wQRam4paRbHvLQA+w5CJOCno4BCu=NFRLRhYhtRw@mail.gmail.com\n\nBackpatch-through: master","shortMessageHtmlLink":"doc PG 17 relnotes: adjust IN wording"}},{"before":"7c655a04a2dc84b59ed6dce97bd38b79e734ecca","after":"4013a5ada25241ead6a3265d6edf9aadb654dc00","ref":"refs/heads/master","pushedAt":"2024-05-27T17:40:35.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Fix check for memory allocation\n\nCommit 61461a300c1 accidentally checked memory allocation success\nusing the wrong variable.\n\nAuthor: Ranier Vilela <ranier.vf@gmail.com>\nReviewed-by: Jelte Fennema-Nio <postgres@jeltef.nl>\nReviewed-by: Daniel Gustafsson <daniel@yesql.se>\nDiscussion: https://postgr.es/m/CAEudQAqQFTH7xCB-+K6zEKjfqbhqCxcr_w4DuJTxVT6h3vzu2w@mail.gmail.com","shortMessageHtmlLink":"Fix check for memory allocation"}},{"before":"8285b484a47d829a29fbe0ebe65cdc9f9dfb179d","after":"7c655a04a2dc84b59ed6dce97bd38b79e734ecca","ref":"refs/heads/master","pushedAt":"2024-05-26T21:40:58.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Fix meson uuid header check so it works with MSVC\n\nThe OSSP uuid.h file includes unistd.h, so to use it with MSVC we need to\ninclude the postgres include directories so it picks up our version of\nthat in src/include/port/win32_msvc. Adjust the meson test accordingly.","shortMessageHtmlLink":"Fix meson uuid header check so it works with MSVC"}},{"before":"945ec4c4bca1e1c4347cd3f93135e96770ac1b4c","after":"8285b484a47d829a29fbe0ebe65cdc9f9dfb179d","ref":"refs/heads/master","pushedAt":"2024-05-26T11:58:51.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Fix potential NULL pointer dereference in getIdentitySequence()\n\nThe function invokes SearchSysCacheAttNum() and SearchSysCacheAttName().\nThey may respectively return 0 for the attribute number or NULL for\nthe attribute name if the attribute does not exist, without any kind of\nerror handling.  The common practice is to check that the data retrieved\nfrom the syscache is valid.  There is no risk of NULL pointer\ndereferences currently, but let's stick to the practice of making sure\nthat this data is always valid, to catch future inconsistency mistakes.\nThe code is switched to use get_attnum() and get_attname(), and adds\nsome error handling.\n\nOversight in 509199587df7.\n\nReported-by: Ranier Vilela\nAuthor: Ashutosh Bapat\nDiscussion: https://postgr.es/m/CAEudQAqh_RZqoFcYKso5d9VhF-Vd64_ZodfQ_2zSusszkEmyRg@mail.gmail.com","shortMessageHtmlLink":"Fix potential NULL pointer dereference in getIdentitySequence()"}},{"before":"4cf9aab2147683100a79bf66a2aa87811674d66c","after":"945ec4c4bca1e1c4347cd3f93135e96770ac1b4c","ref":"refs/heads/master","pushedAt":"2024-05-26T04:14:32.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"amcheck: Fixes for right page check during unique constraint check\n\n * Don't forget to pfree() the right page when it's to be ignored.\n * Report error on unexpected non-leaf right page even if this page is not\n   to be ignored.  This restores the logic which was unintendedly changed\n   in 97e5b0026f.\n\nReported-by: Pavel Borisov","shortMessageHtmlLink":"amcheck: Fixes for right page check during unique constraint check"}},{"before":"f3bfa029911c02470bcd8dcc8d707aef52f77de7","after":"4cf9aab2147683100a79bf66a2aa87811674d66c","ref":"refs/heads/master","pushedAt":"2024-05-26T03:56:34.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"doc PG 17 relnotes:  improve btree \"set/array\" matching item\n\nReported-by: Peter Geoghegan\n\nDiscussion: https://postgr.es/m/CAH2-WznwSs5irUka2deUooSdH7Sts2oPdVv4PCOwhK51fq2ZTg@mail.gmail.com\n\nBackpatch-through: master","shortMessageHtmlLink":"doc PG 17 relnotes: improve btree \"set/array\" matching item"}},{"before":"232278ca93f95bb6a0ea756bf7cf79928118bc1e","after":"f3bfa029911c02470bcd8dcc8d707aef52f77de7","ref":"refs/heads/master","pushedAt":"2024-05-26T03:50:47.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"doc PG 17 relnotes:  fix \"pg_stat_slru_reset\" wording\n\nReported-by: Marcos Pegoraro\n\nDiscussion: https://postgr.es/m/CAB-JLwYXrL-8FBfVDX8tevyTJ8y1SMmot5A-5cLqXAAne7W0CQ@mail.gmail.com\n\nBackpatch-through: master","shortMessageHtmlLink":"doc PG 17 relnotes: fix \"pg_stat_slru_reset\" wording"}},{"before":"d53a4286d772c50ad7a8ff72ca637de613532592","after":"232278ca93f95bb6a0ea756bf7cf79928118bc1e","ref":"refs/heads/master","pushedAt":"2024-05-26T03:48:41.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"doc PG 17 relnote:  adjust \"SLRU cache sizes to be configured\"\n\nAdd Álvaro Herrera as additional item author.\n\nReported-by: Álvaro Herrera\n\nDiscussion: https://postgr.es/m/202405231122.zew2gncy63fo@alvherre.pgsql\n\nAuthor: Álvaro Herrera\n\nBackpatch-through: master","shortMessageHtmlLink":"doc PG 17 relnote: adjust \"SLRU cache sizes to be configured\""}},{"before":"87331c68233425dd02048978e527dcf1ca505c6d","after":"d53a4286d772c50ad7a8ff72ca637de613532592","ref":"refs/heads/master","pushedAt":"2024-05-26T03:47:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Provide deterministic order for catalog queries in partition_split.sql\n\nSystem catalog tables are subject to modification by parallel tests.  This\nis the source of instability when querying them without explicit ORDER BY.\nThis commit adds explicit ORDER BY to system catalog queries in\npartition_split.sql to stabilize the result.\n\nReported-by: Tom Lane\nDiscussion: https://postgr.es/m/695264.1716578979%40sss.pgh.pa.us","shortMessageHtmlLink":"Provide deterministic order for catalog queries in partition_split.sql"}},{"before":"53785d2a2aaa7899eb82fb4eba9af6da83680c8d","after":"87331c68233425dd02048978e527dcf1ca505c6d","ref":"refs/heads/master","pushedAt":"2024-05-26T03:40:46.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"doc PG 17 relnotes:  combine items\n\nReported-by: Andres Freund\n\nDiscussion: https://postgr.es/m/20240524182329.gmzcd3a2zrvyepgy@awork3.anarazel.de\n\nBackpatch-through: master","shortMessageHtmlLink":"doc PG 17 relnotes: combine items"}},{"before":"ac8c85d04b133509071b1de60a027ebe00654696","after":"53785d2a2aaa7899eb82fb4eba9af6da83680c8d","ref":"refs/heads/master","pushedAt":"2024-05-24T04:42:49.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Fix comment in 024_add_drop_pub.pl\n\nA comment of the test was referring to an incorrect table.\n\nThinko in 1046a69b3087.\n\nExtracted from a larger patch by the same author.\n\nAuthor: Alexander Lakhin\nDiscussion: https://postgr.es/m/70b340bc-244a-589d-ef8b-d8aebb707a84@gmail.com","shortMessageHtmlLink":"Fix comment in 024_add_drop_pub.pl"}},{"before":"78030a66d75b19a6428f30e31b12bc6059c1fff3","after":"338fb8714c6cfe30c567ecb79812ec3879bd117f","ref":"refs/heads/REL_16_STABLE","pushedAt":"2024-05-24T02:22:00.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Improve stability of subscription/029_on_error.pl\n\nThis test was failing when using wal_debug=on and -DWAL_DEBUG because of\nadditional log entries that made the test grab an LSN not mapping with\nthe error expected in the test.\n\nPreviously the test would look for the first matching line to get the\nLSN to skip up to.  This is improved by having the test scan the logs\nwith a regexp that checks for the expected ERROR string, ensuring that\nthe wanted LSN comes from the correct context.\n\nBackpatch down to 15 where this test has been introduced.\n\nAuthor: Ian Ilyasov\nDiscussion: https://postgr.es/m/GV1P251MB100415F17E6B2FDD7188777ECDE32@GV1P251MB1004.EURP251.PROD.OUTLOOK.COM\nBackpatch-through: 15","shortMessageHtmlLink":"Improve stability of subscription/029_on_error.pl"}},{"before":"e892e72b3c8ce9221003cddca6b8a88e2c951cad","after":"8e16f81f3db4eb03ac2195e9e5527852047c14a0","ref":"refs/heads/REL_15_STABLE","pushedAt":"2024-05-24T02:22:00.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Improve stability of subscription/029_on_error.pl\n\nThis test was failing when using wal_debug=on and -DWAL_DEBUG because of\nadditional log entries that made the test grab an LSN not mapping with\nthe error expected in the test.\n\nPreviously the test would look for the first matching line to get the\nLSN to skip up to.  This is improved by having the test scan the logs\nwith a regexp that checks for the expected ERROR string, ensuring that\nthe wanted LSN comes from the correct context.\n\nBackpatch down to 15 where this test has been introduced.\n\nAuthor: Ian Ilyasov\nDiscussion: https://postgr.es/m/GV1P251MB100415F17E6B2FDD7188777ECDE32@GV1P251MB1004.EURP251.PROD.OUTLOOK.COM\nBackpatch-through: 15","shortMessageHtmlLink":"Improve stability of subscription/029_on_error.pl"}},{"before":"0162a9bde267a0dc88f35a8d286514c059e1e0e2","after":"ac8c85d04b133509071b1de60a027ebe00654696","ref":"refs/heads/master","pushedAt":"2024-05-24T02:22:00.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Improve stability of subscription/029_on_error.pl\n\nThis test was failing when using wal_debug=on and -DWAL_DEBUG because of\nadditional log entries that made the test grab an LSN not mapping with\nthe error expected in the test.\n\nPreviously the test would look for the first matching line to get the\nLSN to skip up to.  This is improved by having the test scan the logs\nwith a regexp that checks for the expected ERROR string, ensuring that\nthe wanted LSN comes from the correct context.\n\nBackpatch down to 15 where this test has been introduced.\n\nAuthor: Ian Ilyasov\nDiscussion: https://postgr.es/m/GV1P251MB100415F17E6B2FDD7188777ECDE32@GV1P251MB1004.EURP251.PROD.OUTLOOK.COM\nBackpatch-through: 15","shortMessageHtmlLink":"Improve stability of subscription/029_on_error.pl"}},{"before":"da32f5c4bca7f3447b869de2afbbfa0b74443d45","after":"0162a9bde267a0dc88f35a8d286514c059e1e0e2","ref":"refs/heads/master","pushedAt":"2024-05-23T19:52:32.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Remove race conditions between ECPGdebug() and ecpg_log().\n\nCoverity complains that ECPGdebug is accessing debugstream without\nholding debug_mutex, which is a fair complaint: we should take\ndebug_mutex while changing the settings ecpg_log looks at.\n\nIn some branches it also complains about unlocked use of simple_debug.\nI think it's intentional and safe to have a quick unlocked check of\nsimple_debug at the start of ecpg_log, since that early exit will\nalways be taken in non-debug cases.  But we should recheck\nsimple_debug after acquiring the mutex.  In the worst case, calling\nECPGdebug concurrently with ecpg_log in another thread could result\nin a null-pointer dereference due to debugstream transiently being\nNULL while simple_debug isn't 0.\n\nThis is largely hypothetical, since it's unlikely anybody uses\nECPGdebug() at all in the field, and our own regression tests\ndon't seem to be hitting the theoretical race conditions either.\nStill, if we're going to the trouble of having mutexes here, we ought\nto be using them in a way that's actually safe not just almost safe.\nHence, back-patch to all supported branches.","shortMessageHtmlLink":"Remove race conditions between ECPGdebug() and ecpg_log()."}},{"before":"961608636461e259487223237147ce447672deaa","after":"0795a35d13089c203f1b1ef523824c2fc22a6af9","ref":"refs/heads/REL_14_STABLE","pushedAt":"2024-05-23T19:52:32.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Remove race conditions between ECPGdebug() and ecpg_log().\n\nCoverity complains that ECPGdebug is accessing debugstream without\nholding debug_mutex, which is a fair complaint: we should take\ndebug_mutex while changing the settings ecpg_log looks at.\n\nIn some branches it also complains about unlocked use of simple_debug.\nI think it's intentional and safe to have a quick unlocked check of\nsimple_debug at the start of ecpg_log, since that early exit will\nalways be taken in non-debug cases.  But we should recheck\nsimple_debug after acquiring the mutex.  In the worst case, calling\nECPGdebug concurrently with ecpg_log in another thread could result\nin a null-pointer dereference due to debugstream transiently being\nNULL while simple_debug isn't 0.\n\nThis is largely hypothetical, since it's unlikely anybody uses\nECPGdebug() at all in the field, and our own regression tests\ndon't seem to be hitting the theoretical race conditions either.\nStill, if we're going to the trouble of having mutexes here, we ought\nto be using them in a way that's actually safe not just almost safe.\nHence, back-patch to all supported branches.","shortMessageHtmlLink":"Remove race conditions between ECPGdebug() and ecpg_log()."}},{"before":"0c6b6498131e0552d5bb120bdcbf72ffbcd524fa","after":"2e062b65539ea9f85cf591ffbc4cd2db30bf5f51","ref":"refs/heads/REL_13_STABLE","pushedAt":"2024-05-23T19:52:32.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"postgres-mirror","name":"Postgres Mirrorbot","path":"/postgres-mirror","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/368201?s=80&v=4"},"commit":{"message":"Remove race conditions between ECPGdebug() and ecpg_log().\n\nCoverity complains that ECPGdebug is accessing debugstream without\nholding debug_mutex, which is a fair complaint: we should take\ndebug_mutex while changing the settings ecpg_log looks at.\n\nIn some branches it also complains about unlocked use of simple_debug.\nI think it's intentional and safe to have a quick unlocked check of\nsimple_debug at the start of ecpg_log, since that early exit will\nalways be taken in non-debug cases.  But we should recheck\nsimple_debug after acquiring the mutex.  In the worst case, calling\nECPGdebug concurrently with ecpg_log in another thread could result\nin a null-pointer dereference due to debugstream transiently being\nNULL while simple_debug isn't 0.\n\nThis is largely hypothetical, since it's unlikely anybody uses\nECPGdebug() at all in the field, and our own regression tests\ndon't seem to be hitting the theoretical race conditions either.\nStill, if we're going to the trouble of having mutexes here, we ought\nto be using them in a way that's actually safe not just almost safe.\nHence, back-patch to all supported branches.","shortMessageHtmlLink":"Remove race conditions between ECPGdebug() and ecpg_log()."}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEW-ljrwA","startCursor":null,"endCursor":null}},"title":"Activity · postgres/postgres"}