{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":178367123,"defaultBranch":"IVM","name":"pgsql-ivm","ownerLogin":"sraoss","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2019-03-29T08:45:05.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/5737736?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1694008748.0","currentOid":""},"activityList":{"items":[{"before":"241ef53b6a95be0c7c175cbad48e5492dc3ae29c","after":"a134baea7ab0cc907b9d9d3d16f9ac97ec8200be","ref":"refs/heads/REL_12_STABLE","pushedAt":"2024-07-11T03:38:32.000Z","pushType":"push","commitsCount":9,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Make our back branches compatible with libxml2 2.13.x.\n\nThis back-patches HEAD commits 066e8ac6e, 6082b3d5d, e7192486d,\nand 896cd266f into supported branches.  Changes:\n\n* Use xmlAddChildList not xmlAddChild in XMLSERIALIZE\n(affects v16 and up only).  This was a flat-out coding mistake\nthat we got away with due to lax checking in previous versions\nof xmlAddChild.\n\n* Use xmlParseInNodeContext not xmlParseBalancedChunkMemory.\nThis is to dodge a bug in xmlParseBalancedChunkMemory in libxm2\nreleases 2.13.0-2.13.2.  While that bug is now fixed upstream and\nwill probably never be seen in any production-oriented distro, it is\ncurrently a problem on some more-bleeding-edge-friendly platforms.\n\n* Suppress \"chunk is not well balanced\" errors from libxml2,\nunless it is the only error.  This eliminates an error-reporting\ndiscrepancy between 2.13 and older releases.  This error is\nalmost always redundant with previous errors, if not flat-out\ninappropriate, which is why 2.13 changed the behavior and why\nnobody's likely to miss it.\n\nErik Wienhold and Tom Lane, per report from Frank Streitzig.\n\nDiscussion: https://postgr.es/m/trinity-b0161630-d230-4598-9ebc-7a23acdb37cb-1720186432160@3c-app-gmx-bap25\nDiscussion: https://postgr.es/m/trinity-361ba18b-541a-4fe7-bc63-655ae3a7d599-1720259822452@3c-app-gmx-bs01","shortMessageHtmlLink":"Make our back branches compatible with libxml2 2.13.x."}},{"before":"0d80e59a1b2cd546daed3c5133fa2db140c8ca6c","after":"48132587d9bc752ec5d35f3a6369b83b3722e423","ref":"refs/heads/REL_13_STABLE","pushedAt":"2024-07-11T03:38:30.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Make our back branches compatible with libxml2 2.13.x.\n\nThis back-patches HEAD commits 066e8ac6e, 6082b3d5d, e7192486d,\nand 896cd266f into supported branches.  Changes:\n\n* Use xmlAddChildList not xmlAddChild in XMLSERIALIZE\n(affects v16 and up only).  This was a flat-out coding mistake\nthat we got away with due to lax checking in previous versions\nof xmlAddChild.\n\n* Use xmlParseInNodeContext not xmlParseBalancedChunkMemory.\nThis is to dodge a bug in xmlParseBalancedChunkMemory in libxm2\nreleases 2.13.0-2.13.2.  While that bug is now fixed upstream and\nwill probably never be seen in any production-oriented distro, it is\ncurrently a problem on some more-bleeding-edge-friendly platforms.\n\n* Suppress \"chunk is not well balanced\" errors from libxml2,\nunless it is the only error.  This eliminates an error-reporting\ndiscrepancy between 2.13 and older releases.  This error is\nalmost always redundant with previous errors, if not flat-out\ninappropriate, which is why 2.13 changed the behavior and why\nnobody's likely to miss it.\n\nErik Wienhold and Tom Lane, per report from Frank Streitzig.\n\nDiscussion: https://postgr.es/m/trinity-b0161630-d230-4598-9ebc-7a23acdb37cb-1720186432160@3c-app-gmx-bap25\nDiscussion: https://postgr.es/m/trinity-361ba18b-541a-4fe7-bc63-655ae3a7d599-1720259822452@3c-app-gmx-bs01","shortMessageHtmlLink":"Make our back branches compatible with libxml2 2.13.x."}},{"before":"4867f8a555cea1bc6de1726b0030896aa4cd3c70","after":"21471f18e9d9aa3383314ed8bc9163bc369109ae","ref":"refs/heads/master","pushedAt":"2024-07-11T03:38:28.000Z","pushType":"push","commitsCount":74,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Add PgStat_KindInfo.init_shmem_cb\n\nThis new callback gives fixed-numbered stats the possibility to take\nactions based on the area of shared memory allocated for them.\n\nThis removes from pgstat_shmem.c any knowledge specific to the types\nof fixed-numbered stats, and the initializations happen in their own\nfiles.  Like b68b29bc8fec, this change is useful to make this area of\nthe code more pluggable, so as custom fixed-numbered stats can take\nactions after their shared memory area is initialized.\n\nReviewed-by: Bertrand Drouvot\nDiscussion: https://postgr.es/m/Zot5bxoPYdS7yaoy@paquier.xyz","shortMessageHtmlLink":"Add PgStat_KindInfo.init_shmem_cb"}},{"before":"bfa3d27906646f39599901891a237a736191ffc9","after":"0536f8e2cca21aad53eb11b39513e96e5f0f0830","ref":"refs/heads/REL9_5_STABLE","pushedAt":"2024-07-02T07:38:50.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Remove redundant perl version checks\n\nCommit 4c1532763a removed some redundant uses of 'use 5.008001;' in perl\nscripts, including in plperl's plc_perlboot.pl. Because it made other\nchanges it wasn't backpatched. However, now this is causing a failure on\nback branches when built with bleeding edge perl. Therefore, backpatch\njust that part of it which removed those uses, from 15 all the way down\nto 9.2, which is the earliest version currently built in the buildfarm.\n\nper report from Alexander Lakhin\n\nDiscussion: https://postgr.es/m/4cc2ee93-e03c-8e13-61ed-412e7e6ff19d@gmail.com","shortMessageHtmlLink":"Remove redundant perl version checks"}},{"before":"3911fd55f53a930fcca6bc4889209021cc50ec2f","after":"12c8faaa7b59b99d56ddb730480645725bf4fa76","ref":"refs/heads/REL9_6_STABLE","pushedAt":"2024-07-02T07:38:49.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Remove redundant perl version checks\n\nCommit 4c1532763a removed some redundant uses of 'use 5.008001;' in perl\nscripts, including in plperl's plc_perlboot.pl. Because it made other\nchanges it wasn't backpatched. However, now this is causing a failure on\nback branches when built with bleeding edge perl. Therefore, backpatch\njust that part of it which removed those uses, from 15 all the way down\nto 9.2, which is the earliest version currently built in the buildfarm.\n\nper report from Alexander Lakhin\n\nDiscussion: https://postgr.es/m/4cc2ee93-e03c-8e13-61ed-412e7e6ff19d@gmail.com","shortMessageHtmlLink":"Remove redundant perl version checks"}},{"before":"c18c12c983a84d55e58b176969782c7ffac3272b","after":"320534f8f25bf5aa2de4ad1f561b71219cb4e5ff","ref":"refs/heads/REL_10_STABLE","pushedAt":"2024-07-02T07:38:47.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Remove redundant perl version checks\n\nCommit 4c1532763a removed some redundant uses of 'use 5.008001;' in perl\nscripts, including in plperl's plc_perlboot.pl. Because it made other\nchanges it wasn't backpatched. However, now this is causing a failure on\nback branches when built with bleeding edge perl. Therefore, backpatch\njust that part of it which removed those uses, from 15 all the way down\nto 9.2, which is the earliest version currently built in the buildfarm.\n\nper report from Alexander Lakhin\n\nDiscussion: https://postgr.es/m/4cc2ee93-e03c-8e13-61ed-412e7e6ff19d@gmail.com","shortMessageHtmlLink":"Remove redundant perl version checks"}},{"before":"fd851f9e4a13d81cccc4ac5d6059d732c7518111","after":"e1541d518821e88344790c2d046e4f9d770fbf66","ref":"refs/heads/REL_11_STABLE","pushedAt":"2024-07-02T07:38:45.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Remove redundant perl version checks\n\nCommit 4c1532763a removed some redundant uses of 'use 5.008001;' in perl\nscripts, including in plperl's plc_perlboot.pl. Because it made other\nchanges it wasn't backpatched. However, now this is causing a failure on\nback branches when built with bleeding edge perl. Therefore, backpatch\njust that part of it which removed those uses, from 15 all the way down\nto 9.2, which is the earliest version currently built in the buildfarm.\n\nper report from Alexander Lakhin\n\nDiscussion: https://postgr.es/m/4cc2ee93-e03c-8e13-61ed-412e7e6ff19d@gmail.com","shortMessageHtmlLink":"Remove redundant perl version checks"}},{"before":"25675c474292dca71470ef17ea8a53c150eb0e0a","after":"241ef53b6a95be0c7c175cbad48e5492dc3ae29c","ref":"refs/heads/REL_12_STABLE","pushedAt":"2024-07-02T07:38:44.000Z","pushType":"push","commitsCount":73,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Fix missing installation/uninstallation rules for BackgroundPsql.pm\n\nCommit d5fd7865 backported BackgroundPsql perl module module with\nhelper functions for tests running interactive or background psql\ntasks to PG 12 to 15, but did not add installation/uninstallation\nrules of the build system, causing problems running TAP tests for the\nextensions.\n\nAuthor: Pavan Deolasee <pavan.deolasee@gmail.com>\nDiscussion: https://www.postgresql.org/message-id/CABOikdPmRuZrcf_gtgXmQzZ5Tbg9yUJmqXDCAZ2aW%3DWi-PbDyQ%40mail.gmail.com","shortMessageHtmlLink":"Fix missing installation/uninstallation rules for BackgroundPsql.pm"}},{"before":"de3c5b18729a234df0b9203e195a2a5c168ef1cd","after":"0d80e59a1b2cd546daed3c5133fa2db140c8ca6c","ref":"refs/heads/REL_13_STABLE","pushedAt":"2024-07-02T07:38:41.000Z","pushType":"push","commitsCount":77,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Fix missing installation/uninstallation rules for BackgroundPsql.pm\n\nCommit d5fd7865 backported BackgroundPsql perl module module with\nhelper functions for tests running interactive or background psql\ntasks to PG 12 to 15, but did not add installation/uninstallation\nrules of the build system, causing problems running TAP tests for the\nextensions.\n\nAuthor: Pavan Deolasee <pavan.deolasee@gmail.com>\nDiscussion: https://www.postgresql.org/message-id/CABOikdPmRuZrcf_gtgXmQzZ5Tbg9yUJmqXDCAZ2aW%3DWi-PbDyQ%40mail.gmail.com","shortMessageHtmlLink":"Fix missing installation/uninstallation rules for BackgroundPsql.pm"}},{"before":"f4ad0021aface01ee74604355bd2e998e5f73320","after":"4867f8a555cea1bc6de1726b0030896aa4cd3c70","ref":"refs/heads/master","pushedAt":"2024-07-02T07:38:39.000Z","pushType":"push","commitsCount":671,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Drop pre-existing subscriptions from the converted subscriber.\n\nWe don't need the pre-existing subscriptions on the newly formed\nsubscriber by using pg_createsubscriber. The apply workers corresponding\nto these subscriptions can connect to other publisher nodes and either get\nsome unwarranted data or can lead to ERRORs in connecting to such nodes.\n\nAuthor: Kuroda Hayato\nReviewed-by: Amit Kapila, Shlok Kyal, Vignesh C\nBackpatch-through: 17\nDiscussion: https://postgr.es/m/OSBPR01MB25526A30A1FBF863ACCDDA3AF5C92@OSBPR01MB2552.jpnprd01.prod.outlook.com","shortMessageHtmlLink":"Drop pre-existing subscriptions from the converted subscriber."}},{"before":"0075d78947e3800c5a807f48fd901f16db91101b","after":"f4ad0021aface01ee74604355bd2e998e5f73320","ref":"refs/heads/master","pushedAt":"2024-03-31T13:43:43.000Z","pushType":"push","commitsCount":14,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Revert \"Speed up tail processing when hashing aligned C strings\"\n\nThis reverts commit 07f0f6abfc7f6c55cede528d9689dedecefc734a.\n\nThis has shown failures on both Valgrind and big-endian machines,\nper members skink and pike.","shortMessageHtmlLink":"Revert \"Speed up tail processing when hashing aligned C strings\""}},{"before":"24dc4afebd5a82f30aed6bd18d48ff42ef787410","after":"25675c474292dca71470ef17ea8a53c150eb0e0a","ref":"refs/heads/REL_12_STABLE","pushedAt":"2024-03-29T11:46:50.000Z","pushType":"push","commitsCount":20,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Fix unnecessary use of moving-aggregate mode with non-moving frame.\n\nWhen a plain aggregate is used as a window function, and the window\nframe start is specified as UNBOUNDED PRECEDING, the frame's head\ncannot move so we do not need to use moving-aggregate mode.  The check\nfor that was put into initialize_peragg(), failing to notice that\nExecInitWindowAgg() calls that function before it's filled in\nwinstate->frameOptions.  Since makeNode() would have zeroed the field,\nthis didn't provoke uninitialized-value complaints, nor would the\nerroneous decision have resulted in more than a little inefficiency.\nStill, it's wrong, so move the initialization of\nwinstate->frameOptions earlier to make it work properly.\n\nWhile here, also fix a thinko in a comment.  Both errors crept in in\ncommit a9d9acbf2 which introduced the moving-aggregate mode.\n\nSpotted by Vallimaharajan G.  Back-patch to all supported branches.\n\nDiscussion: https://postgr.es/m/18e7f2a5167.fe36253866818.977923893562469143@zohocorp.com","shortMessageHtmlLink":"Fix unnecessary use of moving-aggregate mode with non-moving frame."}},{"before":"d5c3d6ca0152b8ea4870effcd49521e4f767ccac","after":"de3c5b18729a234df0b9203e195a2a5c168ef1cd","ref":"refs/heads/REL_13_STABLE","pushedAt":"2024-03-29T11:46:48.000Z","pushType":"push","commitsCount":22,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Fix unnecessary use of moving-aggregate mode with non-moving frame.\n\nWhen a plain aggregate is used as a window function, and the window\nframe start is specified as UNBOUNDED PRECEDING, the frame's head\ncannot move so we do not need to use moving-aggregate mode.  The check\nfor that was put into initialize_peragg(), failing to notice that\nExecInitWindowAgg() calls that function before it's filled in\nwinstate->frameOptions.  Since makeNode() would have zeroed the field,\nthis didn't provoke uninitialized-value complaints, nor would the\nerroneous decision have resulted in more than a little inefficiency.\nStill, it's wrong, so move the initialization of\nwinstate->frameOptions earlier to make it work properly.\n\nWhile here, also fix a thinko in a comment.  Both errors crept in in\ncommit a9d9acbf2 which introduced the moving-aggregate mode.\n\nSpotted by Vallimaharajan G.  Back-patch to all supported branches.\n\nDiscussion: https://postgr.es/m/18e7f2a5167.fe36253866818.977923893562469143@zohocorp.com","shortMessageHtmlLink":"Fix unnecessary use of moving-aggregate mode with non-moving frame."}},{"before":"07c36c1333e00df5a4baf6b04ba2f3f300f57d69","after":"0075d78947e3800c5a807f48fd901f16db91101b","ref":"refs/heads/master","pushedAt":"2024-03-29T11:46:46.000Z","pushType":"push","commitsCount":291,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Allow \"internal\" subtransactions in parallel mode.\n\nAllow use of BeginInternalSubTransaction() in parallel mode, so long\nas the subtransaction doesn't attempt to acquire an XID or increment\nthe command counter.  Given those restrictions, the other parallel\nprocesses don't need to know about the subtransaction at all, so\nthis should be safe.  The benefit is that it allows subtransactions\nintended for error recovery, such as pl/pgsql exception blocks,\nto be used in PARALLEL SAFE functions.\n\nAnother reason for doing this is that the API of\nBeginInternalSubTransaction() doesn't allow reporting failure.\npl/python for one, and perhaps other PLs, copes very poorly with an\nerror longjmp out of BeginInternalSubTransaction().  The headline\nfeature of this patch removes the only easily-triggerable failure\ncase within that function.  There remain some resource-exhaustion\nand similar cases, which we now deal with by promoting them to FATAL\nerrors, so that callers need not try to clean up.  (It is likely\nthat such errors would leave us with corrupted transaction state\ninside xact.c, making recovery difficult if not impossible anyway.)\n\nAlthough this work started because of a report of a pl/python crash,\nwe're not going to do anything about that in the back branches.\nBack-patching this particular fix is obviously not very wise.\nWhile we could contemplate some narrower band-aid, pl/python is\nalready an untrusted language, so it seems okay to classify this\nas a \"so don't do that\" case.\n\nPatch by me, per report from Hao Zhang.  Thanks to Robert Haas for\nreview.\n\nDiscussion: https://postgr.es/m/CALY6Dr-2yLVeVPhNMhuBnRgOZo1UjoTETgtKBx1B2gUi8yy+3g@mail.gmail.com","shortMessageHtmlLink":"Allow \"internal\" subtransactions in parallel mode."}},{"before":"655dc310460c601d434d05339b7fa46ed97675b3","after":"07c36c1333e00df5a4baf6b04ba2f3f300f57d69","ref":"refs/heads/master","pushedAt":"2024-03-04T03:55:50.000Z","pushType":"push","commitsCount":10,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Support partition pruning on boolcol IS [NOT] UNKNOWN\n\nWhile working on 4c2369ac5, I noticed we went out of our way not to\nsupport clauses on boolean partitioned tables in the form of \"IS\nUNKNOWN\" and \"IS NOT UNKNOWN\".  It's almost as much code to disallow\nthis as it is to allow it, so let's allow it.\n\nDiscussion: https://postgr.es/m/CAApHDvobKtcN6+xOuOfcutfp6T7jP=JPA9y3=MAEqnuKdDsQrw@mail.gmail.com","shortMessageHtmlLink":"Support partition pruning on boolcol IS [NOT] UNKNOWN"}},{"before":"dd9779141eacbad08670fc4d55d7e076301ba69a","after":"fd851f9e4a13d81cccc4ac5d6059d732c7518111","ref":"refs/heads/REL_11_STABLE","pushedAt":"2024-03-01T16:35:41.000Z","pushType":"push","commitsCount":77,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Stamp 11.22.","shortMessageHtmlLink":"Stamp 11.22."}},{"before":"f06e1711d2e64aa6f56fe7aee49d56ea085ed002","after":"24dc4afebd5a82f30aed6bd18d48ff42ef787410","ref":"refs/heads/REL_12_STABLE","pushedAt":"2024-03-01T16:35:40.000Z","pushType":"push","commitsCount":191,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Fix integer underflow in shared memory debugging\n\ndsa_dump would print a large negative number instead of zero for\nsegment bin 0.  Fix by explicitly checking for underflow and add\nspecial case for bin 0. Backpatch to all supported versions.\n\nAuthor: Ian Ilyasov <ianilyasov@outlook.com>\nReviewed-by: Robert Haas <robertmhaas@gmail.com>\nDiscussion: https://postgr.es/m/GV1P251MB1004E0D09D117D3CECF9256ECD502@GV1P251MB1004.EURP251.PROD.OUTLOOK.COM\nBackpatch-through: v12","shortMessageHtmlLink":"Fix integer underflow in shared memory debugging"}},{"before":"27566bcf3c875a7a75c4f5eac76324f2fe24edda","after":"d5c3d6ca0152b8ea4870effcd49521e4f767ccac","ref":"refs/heads/REL_13_STABLE","pushedAt":"2024-03-01T16:35:38.000Z","pushType":"push","commitsCount":197,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Fix integer underflow in shared memory debugging\n\ndsa_dump would print a large negative number instead of zero for\nsegment bin 0.  Fix by explicitly checking for underflow and add\nspecial case for bin 0. Backpatch to all supported versions.\n\nAuthor: Ian Ilyasov <ianilyasov@outlook.com>\nReviewed-by: Robert Haas <robertmhaas@gmail.com>\nDiscussion: https://postgr.es/m/GV1P251MB1004E0D09D117D3CECF9256ECD502@GV1P251MB1004.EURP251.PROD.OUTLOOK.COM\nBackpatch-through: v12","shortMessageHtmlLink":"Fix integer underflow in shared memory debugging"}},{"before":"165d581f146b09543b832513ee00fead132ba6b1","after":"655dc310460c601d434d05339b7fa46ed97675b3","ref":"refs/heads/master","pushedAt":"2024-03-01T16:35:36.000Z","pushType":"push","commitsCount":1174,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Simplify pg_enc2gettext_tbl[] with C99-designated initializer syntax\n\nThis commit switches pg_enc2gettext_tbl[] in encnames.c to use a\nC99-designated initializer syntax.\n\npg_bind_textdomain_codeset() is simplified so as it is possible to do\na direct lookup at the gettext() array with a value of the enum pg_enc\nrather than doing a loop through all its elements, as long as the\nencoding value provided by GetDatabaseEncoding() is in the correct range\nof supported encoding values.  Note that PG_MULE_INTERNAL gains a value\nin the array, pointing to NULL.\n\nAuthor: Jelte Fennema-Nio\nDiscussion: https://postgr.es/m/CAGECzQT3caUbcCcszNewCCmMbCuyP7XNAm60J3ybd6PN5kH2Dw@mail.gmail.com","shortMessageHtmlLink":"Simplify pg_enc2gettext_tbl[] with C99-designated initializer syntax"}},{"before":null,"after":"1e62b83fb2b6002ac690eae0b71262940bc23bf9","ref":"refs/heads/IVM_for_patch_take2","pushedAt":"2023-09-06T13:59:08.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Add documentations about Incremental View Maintenance","shortMessageHtmlLink":"Add documentations about Incremental View Maintenance"}},{"before":"bb45156f342c2cdb88cdd7f9efdc4541e910ec86","after":"165d581f146b09543b832513ee00fead132ba6b1","ref":"refs/heads/master","pushedAt":"2023-08-28T04:51:02.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Tighten handling of \"ago\" in interval values\n\nThis commit Restrict the unit \"ago\" to only appear at the end of the\ninterval.  According to the documentation, a direction can only be\ndefined at the end of an interval, but it was possible to define it in\nthe middle of the string or define it multiple times.\n\nIn spirit, this is similar to the error handling improvements done in\n5b3c5953553b or bcc704b524904.\n\nAuthor: Joseph Koshakow\nReviewed-by: Jacob Champion, Gurjeet Singh, Reid Thompson\nDiscussion: https://postgr.es/m/CAAvxfHd-yNO+XYnUxL=GaNZ1n+eE0V-oE0+-cC1jdjdU0KS3iw@mail.gmail.com","shortMessageHtmlLink":"Tighten handling of \"ago\" in interval values"}},{"before":"0a1ff1d724e8ef71e1d5e602930bec49f0a9053b","after":"dd9779141eacbad08670fc4d55d7e076301ba69a","ref":"refs/heads/REL_11_STABLE","pushedAt":"2023-08-27T18:02:38.000Z","pushType":"push","commitsCount":12,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Silence compiler warning in release 11 and 12 branches\n\nThe offending code is not present in later branches.\n\nDiscussion: https://postgr.es/m/ba2150c1-8485-6597-fafe-4fcd39e49c28@dunslane.net","shortMessageHtmlLink":"Silence compiler warning in release 11 and 12 branches"}},{"before":"9528ae1a18555dd120345409b9257c9354652595","after":"f06e1711d2e64aa6f56fe7aee49d56ea085ed002","ref":"refs/heads/REL_12_STABLE","pushedAt":"2023-08-27T18:02:36.000Z","pushType":"push","commitsCount":11,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Silence compiler warning in release 11 and 12 branches\n\nThe offending code is not present in later branches.\n\nDiscussion: https://postgr.es/m/ba2150c1-8485-6597-fafe-4fcd39e49c28@dunslane.net","shortMessageHtmlLink":"Silence compiler warning in release 11 and 12 branches"}},{"before":"cc20236d15b373839657af3a33c8c52ac694f25c","after":"27566bcf3c875a7a75c4f5eac76324f2fe24edda","ref":"refs/heads/REL_13_STABLE","pushedAt":"2023-08-27T18:02:35.000Z","pushType":"push","commitsCount":10,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Avoid unnecessary plancache revalidation of utility statements.\n\nRevalidation of a plancache entry (after a cache invalidation event)\nrequires acquiring a snapshot.  Normally that is harmless, but not\nif the cached statement is one that needs to run without acquiring a\nsnapshot.  We were already aware of that for TransactionStmts,\nbut for some reason hadn't extrapolated to the other statements that\nPlannedStmtRequiresSnapshot() knows mustn't set a snapshot.  This can\nlead to unexpected failures of commands such as SET TRANSACTION\nISOLATION LEVEL.  We can fix it in the same way, by excluding those\ncommand types from revalidation.\n\nHowever, we can do even better than that: there is no need to\nrevalidate for any statement type for which parse analysis, rewrite,\nand plan steps do nothing interesting, which is nearly all utility\ncommands.  To mechanize this, invent a parser function\nstmt_requires_parse_analysis() that tells whether parse analysis does\nanything beyond wrapping a CMD_UTILITY Query around the raw parse\ntree.  If that's what it does, then rewrite and plan will just\nskip the Query, so that it is not possible for the same raw parse\ntree to produce a different plan tree after cache invalidation.\n\nstmt_requires_parse_analysis() is basically equivalent to the\nexisting function analyze_requires_snapshot(), except that for\nobscure reasons that function omits ReturnStmt and CallStmt.\nIt is unclear whether those were oversights or intentional.\nI have not been able to demonstrate a bug from not acquiring a\nsnapshot while analyzing these commands, but at best it seems mighty\nfragile.  It seems safer to acquire a snapshot for parse analysis of\nthese commands too, which allows making stmt_requires_parse_analysis\nand analyze_requires_snapshot equivalent.\n\nIn passing this fixes a second bug, which is that ResetPlanCache\nwould exclude ReturnStmts and CallStmts from revalidation.\nThat's surely *not* safe, since they contain parsable expressions.\n\nPer bug #18059 from Pavel Kulakov.  Back-patch to all supported\nbranches.\n\nDiscussion: https://postgr.es/m/18059-79c692f036b25346@postgresql.org","shortMessageHtmlLink":"Avoid unnecessary plancache revalidation of utility statements."}},{"before":"81ccbe520f42a9873734c614e4eb521190d8f8e4","after":"bb45156f342c2cdb88cdd7f9efdc4541e910ec86","ref":"refs/heads/master","pushedAt":"2023-08-27T18:02:33.000Z","pushType":"push","commitsCount":93,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Show names of DEALLOCATE as constants in pg_stat_statements\n\nThis commit switches query jumbling so as prepared statement names are\ntreated as constants in DeallocateStmt.  A boolean field is added to\nDeallocateStmt to make a distinction between ALL and named prepared\nstatements, as \"name\" was used to make this difference before, NULL\nmeaning DEALLOCATE ALL.\n\nPrior to this commit, DEALLOCATE was not tracked in pg_stat_statements,\nfor the reason that it was not possible to treat its name parameter as a\nconstant.  Now that query jumbling applies to all the utility nodes,\nthis reason does not apply anymore.\n\nLike 638d42a3c520, this can be a huge advantage for monitoring where\nprepared statement names are randomly generated, preventing bloat in\npg_stat_statements.  A couple of tests are added to track the new\nbehavior.\n\nAuthor: Dagfinn Ilmari Mannsåker, Michael Paquier\nReviewed-by: Julien Rouhaud\nDiscussion: https://postgr.es/m/ZMhT9kNtJJsHw6jK@paquier.xyz","shortMessageHtmlLink":"Show names of DEALLOCATE as constants in pg_stat_statements"}},{"before":"a72b503ca8289bc418094ba3fc37a83ddcbab93b","after":"0a1ff1d724e8ef71e1d5e602930bec49f0a9053b","ref":"refs/heads/REL_11_STABLE","pushedAt":"2023-08-04T07:08:36.000Z","pushType":"push","commitsCount":51,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Doc: update documentation for creating custom scan paths.\n\nCommit f49842d1e added a new callback for custom scan paths, but missed\nupdating the documentation.\n\nBack-patch to all supported branches.\n\nDiscussion: https://postgr.es/m/CAPmGK15ODkN%2B%3DhkBCufj1HBW0x5OTb65Xuy7ryXchMdiCMpx_g%40mail.gmail.com","shortMessageHtmlLink":"Doc: update documentation for creating custom scan paths."}},{"before":"188dad680e8f32308311c4e1edf4955bf33206c5","after":"9528ae1a18555dd120345409b9257c9354652595","ref":"refs/heads/REL_12_STABLE","pushedAt":"2023-08-04T07:08:33.000Z","pushType":"push","commitsCount":54,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Doc: update documentation for creating custom scan paths.\n\nCommit f49842d1e added a new callback for custom scan paths, but missed\nupdating the documentation.\n\nBack-patch to all supported branches.\n\nDiscussion: https://postgr.es/m/CAPmGK15ODkN%2B%3DhkBCufj1HBW0x5OTb65Xuy7ryXchMdiCMpx_g%40mail.gmail.com","shortMessageHtmlLink":"Doc: update documentation for creating custom scan paths."}},{"before":"8f876d15ca93f7b62b5daf07ab896573991eb935","after":"cc20236d15b373839657af3a33c8c52ac694f25c","ref":"refs/heads/REL_13_STABLE","pushedAt":"2023-08-04T07:08:31.000Z","pushType":"push","commitsCount":62,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Doc: update documentation for creating custom scan paths.\n\nCommit f49842d1e added a new callback for custom scan paths, but missed\nupdating the documentation.\n\nBack-patch to all supported branches.\n\nDiscussion: https://postgr.es/m/CAPmGK15ODkN%2B%3DhkBCufj1HBW0x5OTb65Xuy7ryXchMdiCMpx_g%40mail.gmail.com","shortMessageHtmlLink":"Doc: update documentation for creating custom scan paths."}},{"before":"0bcb3ca3b95b2b94de0b337a73aef333e0346c44","after":"81ccbe520f42a9873734c614e4eb521190d8f8e4","ref":"refs/heads/master","pushedAt":"2023-08-04T07:08:29.000Z","pushType":"push","commitsCount":315,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"Simplify some of the logical replication worker-type checks.\n\nAuthor: Peter Smith\nReviewed-by: Hou Zhijie\nDiscussion: http://postgr.es/m/CAHut+Pv-xkEpuPzbEJ=ZSi7Hp2RoGJf=VA-uDRxLi1KHSneFjg@mail.gmail.com","shortMessageHtmlLink":"Simplify some of the logical replication worker-type checks."}},{"before":"fb1a59de0c52609653166aafc6ce8679a9cfe54b","after":"0bcb3ca3b95b2b94de0b337a73aef333e0346c44","ref":"refs/heads/master","pushedAt":"2023-05-30T11:04:54.753Z","pushType":"push","commitsCount":828,"pusher":{"login":"yugo-n","name":"Yugo Nagata","path":"/yugo-n","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3725343?s=80&v=4"},"commit":{"message":"doc:  PG 16 relnotes, adjust auto_explain logging item\n\nReported-by: Dagfinn Ilmari Mannsåker\n\nDiscussion: https://postgr.es/m/878rdctb7o.fsf@wibble.ilmari.org","shortMessageHtmlLink":"doc: PG 16 relnotes, adjust auto_explain logging item"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEfGJcdQA","startCursor":null,"endCursor":null}},"title":"Activity · sraoss/pgsql-ivm"}