{"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":"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 \nReviewed-by: Jelte Fennema-Nio \nReviewed-by: Daniel Gustafsson \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()."}},{"before":"b4f808467a56b69838730164df5a22f946087b82","after":"78030a66d75b19a6428f30e31b12bc6059c1fff3","ref":"refs/heads/REL_16_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":"c0acf25a5cf2d62b60d82e5bb0c553ce9c05a51d","after":"cd8f1c1207994c8b3d41c48a02fa40547ee48bea","ref":"refs/heads/REL_12_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":"c0df15ac7e9ef3870da50fde49c658290f7a0da6","after":"e892e72b3c8ce9221003cddca6b8a88e2c951cad","ref":"refs/heads/REL_15_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":"6ef762938eead1a42024b219311f6ede5dc2104a","after":"da32f5c4bca7f3447b869de2afbbfa0b74443d45","ref":"refs/heads/master","pushedAt":"2024-05-23T07:27:23.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":"jsonapi: Some message style fixes\n\nAdd missing punctuation, and un-gettext-mark an internal error.","shortMessageHtmlLink":"jsonapi: Some message style fixes"}},{"before":"f7ab71ba0c7bcf237403d40269aeea0a0f2551df","after":"6ef762938eead1a42024b219311f6ede5dc2104a","ref":"refs/heads/master","pushedAt":"2024-05-23T06:40:39.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: Clean up title case use","shortMessageHtmlLink":"doc: Clean up title case use"}},{"before":"dd087e1c13bf5f2bcfdc189976aa4e44ed431739","after":"f7ab71ba0c7bcf237403d40269aeea0a0f2551df","ref":"refs/heads/master","pushedAt":"2024-05-23T04:57:02.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 typo and comments related to the recent no-wait lock improvements\n\nThe argument of dontWait at the top of ProcSleep() was documented\nbackwards, and there was a typo in lock.c.\n\nThinkos in 2346df6fc373.\n\nAuthor: Will Mortensen\nReviewed-by: Jingxian Li, Michael Paquier\nDiscussion: https://postgr.es/m/CAMpnoC5f+eiS7tdy8PUpd_LacSTVT-pYpVooKfjHRQQmkHPZ2g@mail.gmail.com","shortMessageHtmlLink":"Fix typo and comments related to the recent no-wait lock improvements"}},{"before":"7f90a5dc368620e097fac8690b8698e75f8eccba","after":"0c6b6498131e0552d5bb120bdcbf72ffbcd524fa","ref":"refs/heads/REL_13_STABLE","pushedAt":"2024-05-23T04:04:08.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: Fix column_name parameter in ALTER MATERIALIZED VIEW\n\nParameter column_name must be an existing column because ALTER\nMATERIALIZED VIEW cannot add new columns. The old description was\nlikely copied from ALTER TABLE.\n\nAuthor: Erik Wienhold\nDiscussion: https://postgr.es/m/6880ca53-7961-4eeb-86d5-6bd05fc2027e@ewie.name\nBackpatch-through: 12","shortMessageHtmlLink":"doc: Fix column_name parameter in ALTER MATERIALIZED VIEW"}},{"before":"1015162c353510854a3c47ad10b78029664ab13a","after":"961608636461e259487223237147ce447672deaa","ref":"refs/heads/REL_14_STABLE","pushedAt":"2024-05-23T04:04:08.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: Fix column_name parameter in ALTER MATERIALIZED VIEW\n\nParameter column_name must be an existing column because ALTER\nMATERIALIZED VIEW cannot add new columns. The old description was\nlikely copied from ALTER TABLE.\n\nAuthor: Erik Wienhold\nDiscussion: https://postgr.es/m/6880ca53-7961-4eeb-86d5-6bd05fc2027e@ewie.name\nBackpatch-through: 12","shortMessageHtmlLink":"doc: Fix column_name parameter in ALTER MATERIALIZED VIEW"}},{"before":"019ea7675c7722ff7f9016b878feea8e7faac608","after":"b4f808467a56b69838730164df5a22f946087b82","ref":"refs/heads/REL_16_STABLE","pushedAt":"2024-05-23T04:04:08.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: Fix column_name parameter in ALTER MATERIALIZED VIEW\n\nParameter column_name must be an existing column because ALTER\nMATERIALIZED VIEW cannot add new columns. The old description was\nlikely copied from ALTER TABLE.\n\nAuthor: Erik Wienhold\nDiscussion: https://postgr.es/m/6880ca53-7961-4eeb-86d5-6bd05fc2027e@ewie.name\nBackpatch-through: 12","shortMessageHtmlLink":"doc: Fix column_name parameter in ALTER MATERIALIZED VIEW"}},{"before":"686c995fc2223426706ee3f2472e220e7aac4041","after":"c0acf25a5cf2d62b60d82e5bb0c553ce9c05a51d","ref":"refs/heads/REL_12_STABLE","pushedAt":"2024-05-23T04:04:08.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: Fix column_name parameter in ALTER MATERIALIZED VIEW\n\nParameter column_name must be an existing column because ALTER\nMATERIALIZED VIEW cannot add new columns. The old description was\nlikely copied from ALTER TABLE.\n\nAuthor: Erik Wienhold\nDiscussion: https://postgr.es/m/6880ca53-7961-4eeb-86d5-6bd05fc2027e@ewie.name\nBackpatch-through: 12","shortMessageHtmlLink":"doc: Fix column_name parameter in ALTER MATERIALIZED VIEW"}},{"before":"2f3cfcf7677ff11ca0ca18b67bd8fc1ea6ae6dd5","after":"c0df15ac7e9ef3870da50fde49c658290f7a0da6","ref":"refs/heads/REL_15_STABLE","pushedAt":"2024-05-23T04:04:08.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: Fix column_name parameter in ALTER MATERIALIZED VIEW\n\nParameter column_name must be an existing column because ALTER\nMATERIALIZED VIEW cannot add new columns. The old description was\nlikely copied from ALTER TABLE.\n\nAuthor: Erik Wienhold\nDiscussion: https://postgr.es/m/6880ca53-7961-4eeb-86d5-6bd05fc2027e@ewie.name\nBackpatch-through: 12","shortMessageHtmlLink":"doc: Fix column_name parameter in ALTER MATERIALIZED VIEW"}},{"before":"8559252095e17c3cf25a28921a6ef8a14e769519","after":"dd087e1c13bf5f2bcfdc189976aa4e44ed431739","ref":"refs/heads/master","pushedAt":"2024-05-23T04:04:08.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: Fix column_name parameter in ALTER MATERIALIZED VIEW\n\nParameter column_name must be an existing column because ALTER\nMATERIALIZED VIEW cannot add new columns. The old description was\nlikely copied from ALTER TABLE.\n\nAuthor: Erik Wienhold\nDiscussion: https://postgr.es/m/6880ca53-7961-4eeb-86d5-6bd05fc2027e@ewie.name\nBackpatch-through: 12","shortMessageHtmlLink":"doc: Fix column_name parameter in ALTER MATERIALIZED VIEW"}},{"before":"fbd4321fd5b4400fbbf356d686af6ad6d3208c66","after":"8559252095e17c3cf25a28921a6ef8a14e769519","ref":"refs/heads/master","pushedAt":"2024-05-23T03:25:16.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 a couple of outdated comments now that we have MERGE RETURNING\n\nThis has been supported since c649fa24a.\n\nDiscussion: https://postgr.es/m/CAApHDvpqp6vtUzG-_josUEiBGyqnrnVxJ-VdF+hJLXjHdHzsyQ@mail.gmail.com","shortMessageHtmlLink":"Fix a couple of outdated comments now that we have MERGE RETURNING"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEVWvK4gA","startCursor":null,"endCursor":null}},"title":"Activity · postgres/postgres"}