{"commits":[{"author":"Melanie Plageman","commit":"6c8717359a4bba3011d112c094c643372656319f","date":"2026-11-18T16:40:51Z","email":"melanieplageman@gmail.com","id":"01M7QRGMHRSQ1RHMV61RJGM08K","mail_refs":[{"date":"2026-08-27T14:31:21Z","from":"Nazir Bilal Yavuz <byavuz81@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAN55FZ3Lik2m9J+EQjzEHSMSBNgAXU5Myt8LFg=D2OQ0i_jUMQ@mail.gmail.com","subject":"Re: [PATCH] Use streaming read I/O in sample scans","url":"/m/pgsql-hackers/CAN55FZ3Lik2m9J+EQjzEHSMSBNgAXU5Myt8LFg=D2OQ0i_jUMQ@mail.gmail.com/"},{"date":"2026-11-03T06:40:44Z","from":"Bertrand Drouvot <bertranddrouvot.pg@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"aumB7BHGWewR4x/S@bdtpg","subject":"Fix ReadStream handling when heap rescan strategy changes","url":"/m/pgsql-hackers/aumB7BHGWewR4x%2FS@bdtpg/"},{"date":"2026-11-18T22:43:33Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xToNI-00000000IzT-0UT6@gemulon.postgresql.org","subject":"pgsql: Recreate read stream across rescans","url":"/m/pgsql-committers/E1xToNI-00000000IzT-0UT6@gemulon.postgresql.org/"}],"mail_refs_total":3,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"},{"email":"byavuz81@gmail.com","name":"Nazir Bilal Yavuz","person_id":25294249,"role":"reported-by"},{"email":"bertranddrouvot.pg@gmail.com","name":"Bertrand Drouvot","person_id":1050501,"role":"reported-by"},{"email":null,"name":"shihao zhong <zhong950419@gmail.com> (earlier version)","person_id":null,"role":"reviewed-by"},{"email":null,"name":"Joao Rito <joaovictor.rito@gmail.com> (earlier version)","person_id":null,"role":"reviewed-by"}],"subject":"Recreate read stream across rescans"},{"author":"Melanie Plageman","commit":"9107706245e2368b9e3519629761b70cb93993e7","date":"2026-11-18T22:37:06Z","email":"melanieplageman@gmail.com","id":"01M7RCWYJGN3X1CQDPBBNKEJFQ","mail_refs":[{"date":"2026-08-27T14:31:21Z","from":"Nazir Bilal Yavuz <byavuz81@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAN55FZ3Lik2m9J+EQjzEHSMSBNgAXU5Myt8LFg=D2OQ0i_jUMQ@mail.gmail.com","subject":"Re: [PATCH] Use streaming read I/O in sample scans","url":"/m/pgsql-hackers/CAN55FZ3Lik2m9J+EQjzEHSMSBNgAXU5Myt8LFg=D2OQ0i_jUMQ@mail.gmail.com/"},{"date":"2026-11-03T06:40:44Z","from":"Bertrand Drouvot <bertranddrouvot.pg@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"aumB7BHGWewR4x/S@bdtpg","subject":"Fix ReadStream handling when heap rescan strategy changes","url":"/m/pgsql-hackers/aumB7BHGWewR4x%2FS@bdtpg/"},{"date":"2026-11-18T22:39:52Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xToJj-00000000Ixc-2zdK@gemulon.postgresql.org","subject":"pgsql: Recreate read stream across rescans","url":"/m/pgsql-committers/E1xToJj-00000000Ixc-2zdK@gemulon.postgresql.org/"}],"mail_refs_total":3,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"},{"email":"byavuz81@gmail.com","name":"Nazir Bilal Yavuz","person_id":25294249,"role":"reported-by"},{"email":"bertranddrouvot.pg@gmail.com","name":"Bertrand Drouvot","person_id":1050501,"role":"reported-by"},{"email":null,"name":"shihao zhong <zhong950419@gmail.com> (earlier version)","person_id":null,"role":"reviewed-by"},{"email":null,"name":"Joao Rito <joaovictor.rito@gmail.com> (earlier version)","person_id":null,"role":"reviewed-by"}],"subject":"Recreate read stream across rescans"},{"author":"Jeff Davis","commit":"a18df827b6c603973632bd630f5e6ce3adaab9ce","date":"2026-11-18T22:18:37Z","email":"jdavis@postgresql.org","id":"01M7RBV3J81JJASWHJRWBPCEC9","mail_refs":[{"date":"2026-11-06T23:17:48Z","from":"Jeff Davis <pgsql@j-davis.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"62b070d14df4d9d5f44cb8da6f15546c30259053.camel@j-davis.com","subject":"fix special case during recovery for hot_standby=off","url":"/m/pgsql-hackers/62b070d14df4d9d5f44cb8da6f15546c30259053.camel@j-davis.com/"},{"date":"2026-11-18T22:36:53Z","from":"Jeff Davis <jdavis@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xToGq-00000000It1-0Bx4@gemulon.postgresql.org","subject":"pgsql: Recovery: ensure CLOG updates wait for minRecoveryPoint.","url":"/m/pgsql-committers/E1xToGq-00000000It1-0Bx4@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"jdavis@postgresql.org","name":"Jeff Davis","person_id":1008701,"role":"author"},{"email":"ayushtiwari.slg01@gmail.com","name":"Ayush Tiwari","person_id":25294184,"role":"reviewed-by"}],"subject":"Recovery: ensure CLOG updates wait for minRecoveryPoint."},{"author":"Jeff Davis","commit":"8303f2e13c5c2fab539e11054073a58942cb0f30","date":"2026-11-18T22:18:37Z","email":"jdavis@postgresql.org","id":"01M7RBV3J8QE4JPGHH8XNPJ5CZ","mail_refs":[{"date":"2026-11-06T23:17:48Z","from":"Jeff Davis <pgsql@j-davis.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"62b070d14df4d9d5f44cb8da6f15546c30259053.camel@j-davis.com","subject":"fix special case during recovery for hot_standby=off","url":"/m/pgsql-hackers/62b070d14df4d9d5f44cb8da6f15546c30259053.camel@j-davis.com/"},{"date":"2026-11-18T22:36:46Z","from":"Jeff Davis <jdavis@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xToGj-00000000IsM-0HI2@gemulon.postgresql.org","subject":"pgsql: Recovery: ensure CLOG updates wait for minRecoveryPoint.","url":"/m/pgsql-committers/E1xToGj-00000000IsM-0HI2@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"jdavis@postgresql.org","name":"Jeff Davis","person_id":1008701,"role":"author"},{"email":"ayushtiwari.slg01@gmail.com","name":"Ayush Tiwari","person_id":25294184,"role":"reviewed-by"}],"subject":"Recovery: ensure CLOG updates wait for minRecoveryPoint."},{"author":"Melanie Plageman","commit":"e645b48a6921a6293e1b451f2f234cd6aea51be1","date":"2026-11-18T22:35:52Z","email":"melanieplageman@gmail.com","id":"01M7RCTPA0G423VKPFC5NHMZQA","mail_refs":[{"date":"2026-08-27T14:31:21Z","from":"Nazir Bilal Yavuz <byavuz81@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAN55FZ3Lik2m9J+EQjzEHSMSBNgAXU5Myt8LFg=D2OQ0i_jUMQ@mail.gmail.com","subject":"Re: [PATCH] Use streaming read I/O in sample scans","url":"/m/pgsql-hackers/CAN55FZ3Lik2m9J+EQjzEHSMSBNgAXU5Myt8LFg=D2OQ0i_jUMQ@mail.gmail.com/"},{"date":"2026-11-03T06:40:44Z","from":"Bertrand Drouvot <bertranddrouvot.pg@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"aumB7BHGWewR4x/S@bdtpg","subject":"Fix ReadStream handling when heap rescan strategy changes","url":"/m/pgsql-hackers/aumB7BHGWewR4x%2FS@bdtpg/"},{"date":"2026-11-18T22:36:16Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xToGF-00000000Ir8-1hVD@gemulon.postgresql.org","subject":"pgsql: Recreate read stream across rescans","url":"/m/pgsql-committers/E1xToGF-00000000Ir8-1hVD@gemulon.postgresql.org/"}],"mail_refs_total":3,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"},{"email":"byavuz81@gmail.com","name":"Nazir Bilal Yavuz","person_id":25294249,"role":"reported-by"},{"email":"bertranddrouvot.pg@gmail.com","name":"Bertrand Drouvot","person_id":1050501,"role":"reported-by"},{"email":null,"name":"shihao zhong <zhong950419@gmail.com> (earlier version)","person_id":null,"role":"reviewed-by"},{"email":null,"name":"Joao Rito <joaovictor.rito@gmail.com> (earlier version)","person_id":null,"role":"reviewed-by"}],"subject":"Recreate read stream across rescans"},{"author":"Jeff Davis","commit":"6ee74fe7389337a225603fa8ee3c0724e5baa057","date":"2026-11-18T22:18:37Z","email":"jdavis@postgresql.org","id":"01M7RBV3J80GDEQXGRQVWYY8XC","mail_refs":[{"date":"2026-11-06T23:17:48Z","from":"Jeff Davis <pgsql@j-davis.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"62b070d14df4d9d5f44cb8da6f15546c30259053.camel@j-davis.com","subject":"fix special case during recovery for hot_standby=off","url":"/m/pgsql-hackers/62b070d14df4d9d5f44cb8da6f15546c30259053.camel@j-davis.com/"},{"date":"2026-11-18T22:37:11Z","from":"Jeff Davis <jdavis@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xToH8-00000000Ivd-0sdA@gemulon.postgresql.org","subject":"pgsql: Recovery: ensure CLOG updates wait for minRecoveryPoint.","url":"/m/pgsql-committers/E1xToH8-00000000Ivd-0sdA@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"jdavis@postgresql.org","name":"Jeff Davis","person_id":1008701,"role":"author"},{"email":"ayushtiwari.slg01@gmail.com","name":"Ayush Tiwari","person_id":25294184,"role":"reviewed-by"}],"subject":"Recovery: ensure CLOG updates wait for minRecoveryPoint."},{"author":"Jeff Davis","commit":"f8bd8d39783136d849eef57bf227d600f8b3442a","date":"2026-11-18T22:18:37Z","email":"jdavis@postgresql.org","id":"01M7RBV3J87BZM68VEAXXND486","mail_refs":[{"date":"2026-11-06T23:17:48Z","from":"Jeff Davis <pgsql@j-davis.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"62b070d14df4d9d5f44cb8da6f15546c30259053.camel@j-davis.com","subject":"fix special case during recovery for hot_standby=off","url":"/m/pgsql-hackers/62b070d14df4d9d5f44cb8da6f15546c30259053.camel@j-davis.com/"},{"date":"2026-11-18T22:37:07Z","from":"Jeff Davis <jdavis@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xToH4-00000000Iuz-0WIK@gemulon.postgresql.org","subject":"pgsql: Recovery: ensure CLOG updates wait for minRecoveryPoint.","url":"/m/pgsql-committers/E1xToH4-00000000Iuz-0WIK@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"jdavis@postgresql.org","name":"Jeff Davis","person_id":1008701,"role":"author"},{"email":"ayushtiwari.slg01@gmail.com","name":"Ayush Tiwari","person_id":25294184,"role":"reviewed-by"}],"subject":"Recovery: ensure CLOG updates wait for minRecoveryPoint."},{"author":"Jeff Davis","commit":"cff3b4be024d5d9d37004c9a8b2141218a28e9e1","date":"2026-11-18T22:18:37Z","email":"jdavis@postgresql.org","id":"01M7RBV3J8270A5XTMA6A8K254","mail_refs":[{"date":"2026-11-06T23:17:48Z","from":"Jeff Davis <pgsql@j-davis.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"62b070d14df4d9d5f44cb8da6f15546c30259053.camel@j-davis.com","subject":"fix special case during recovery for hot_standby=off","url":"/m/pgsql-hackers/62b070d14df4d9d5f44cb8da6f15546c30259053.camel@j-davis.com/"},{"date":"2026-11-18T22:37:02Z","from":"Jeff Davis <jdavis@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xToGz-00000000IuJ-3i39@gemulon.postgresql.org","subject":"pgsql: Recovery: ensure CLOG updates wait for minRecoveryPoint.","url":"/m/pgsql-committers/E1xToGz-00000000IuJ-3i39@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"jdavis@postgresql.org","name":"Jeff Davis","person_id":1008701,"role":"author"},{"email":"ayushtiwari.slg01@gmail.com","name":"Ayush Tiwari","person_id":25294184,"role":"reviewed-by"}],"subject":"Recovery: ensure CLOG updates wait for minRecoveryPoint."},{"author":"Jeff Davis","commit":"cce784243d5478bdbdb535e0a1d3d06ddc136021","date":"2026-11-18T22:18:37Z","email":"jdavis@postgresql.org","id":"01M7RBV3J82GESS3ZQTF30GNB0","mail_refs":[{"date":"2026-11-06T23:17:48Z","from":"Jeff Davis <pgsql@j-davis.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"62b070d14df4d9d5f44cb8da6f15546c30259053.camel@j-davis.com","subject":"fix special case during recovery for hot_standby=off","url":"/m/pgsql-hackers/62b070d14df4d9d5f44cb8da6f15546c30259053.camel@j-davis.com/"},{"date":"2026-11-18T22:36:57Z","from":"Jeff Davis <jdavis@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xToGu-00000000Itf-3VHq@gemulon.postgresql.org","subject":"pgsql: Recovery: ensure CLOG updates wait for minRecoveryPoint.","url":"/m/pgsql-committers/E1xToGu-00000000Itf-3VHq@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"jdavis@postgresql.org","name":"Jeff Davis","person_id":1008701,"role":"author"},{"email":"ayushtiwari.slg01@gmail.com","name":"Ayush Tiwari","person_id":25294184,"role":"reviewed-by"}],"subject":"Recovery: ensure CLOG updates wait for minRecoveryPoint."},{"author":"Melanie Plageman","commit":"556c025db96500168ed865e26dcfcc3a0b68dbb9","date":"2026-11-18T22:33:43Z","email":"melanieplageman@gmail.com","id":"01M7RCPRAR42YR9B4VWRVGAW5E","mail_refs":[{"date":"2026-08-27T14:31:21Z","from":"Nazir Bilal Yavuz <byavuz81@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAN55FZ3Lik2m9J+EQjzEHSMSBNgAXU5Myt8LFg=D2OQ0i_jUMQ@mail.gmail.com","subject":"Re: [PATCH] Use streaming read I/O in sample scans","url":"/m/pgsql-hackers/CAN55FZ3Lik2m9J+EQjzEHSMSBNgAXU5Myt8LFg=D2OQ0i_jUMQ@mail.gmail.com/"},{"date":"2026-11-03T06:40:44Z","from":"Bertrand Drouvot <bertranddrouvot.pg@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"aumB7BHGWewR4x/S@bdtpg","subject":"Fix ReadStream handling when heap rescan strategy changes","url":"/m/pgsql-hackers/aumB7BHGWewR4x%2FS@bdtpg/"},{"date":"2026-11-18T22:34:52Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xToEt-00000000IqF-1H8a@gemulon.postgresql.org","subject":"pgsql: Recreate read stream across rescans","url":"/m/pgsql-committers/E1xToEt-00000000IqF-1H8a@gemulon.postgresql.org/"}],"mail_refs_total":3,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"},{"email":"byavuz81@gmail.com","name":"Nazir Bilal Yavuz","person_id":25294249,"role":"reported-by"},{"email":"bertranddrouvot.pg@gmail.com","name":"Bertrand Drouvot","person_id":1050501,"role":"reported-by"},{"email":null,"name":"shihao zhong <zhong950419@gmail.com> (earlier version)","person_id":null,"role":"reviewed-by"},{"email":null,"name":"Joao Rito <joaovictor.rito@gmail.com> (earlier version)","person_id":null,"role":"reviewed-by"}],"subject":"Recreate read stream across rescans"},{"author":"David Rowley","commit":"79a9240c6f1394dc10ae40c75b89a9c77934ed73","date":"2026-11-18T20:01:04Z","email":"drowley@postgresql.org","id":"01M7R3Z8007D59YNKXZSZ6FHMD","mail_refs":[{"date":"2026-11-15T04:48:38Z","from":"PG Bug reporting form <noreply@postgresql.org>","how_it_refers":"discussion-trailer","inbox":"pgsql-bugs","message_id":"19904-57a44a8aa7638ae4@postgresql.org","subject":"BUG #19904: pg_column_is_updatable(): \"negative bitmapset member not allowed\" for large attnum (int16 overflow)","url":"/m/pgsql-bugs/19904-57a44a8aa7638ae4@postgresql.org/"},{"date":"2026-11-18T20:09:40Z","from":"David Rowley <drowley@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTlyN-00000000I1K-1bfo@gemulon.postgresql.org","subject":"pgsql: Robustify pg_column_is_updatable() against overly large attnums","url":"/m/pgsql-committers/E1xTlyN-00000000I1K-1bfo@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"drowley@postgresql.org","name":"David Rowley","person_id":1009301,"role":"author"},{"email":"hackerzheng666@gmail.com","name":"Zheng Hacker","person_id":26873974,"role":"reported-by"}],"subject":"Robustify pg_column_is_updatable() against overly large attnums"},{"author":"David Rowley","commit":"94280519a071f33198169066a4d7372c11523a84","date":"2026-11-18T20:01:04Z","email":"drowley@postgresql.org","id":"01M7R3Z800E5DM2XAZKCXW1GBM","mail_refs":[{"date":"2026-11-15T04:48:38Z","from":"PG Bug reporting form <noreply@postgresql.org>","how_it_refers":"discussion-trailer","inbox":"pgsql-bugs","message_id":"19904-57a44a8aa7638ae4@postgresql.org","subject":"BUG #19904: pg_column_is_updatable(): \"negative bitmapset member not allowed\" for large attnum (int16 overflow)","url":"/m/pgsql-bugs/19904-57a44a8aa7638ae4@postgresql.org/"},{"date":"2026-11-18T20:09:29Z","from":"David Rowley <drowley@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTlyC-00000000I0e-43Rc@gemulon.postgresql.org","subject":"pgsql: Robustify pg_column_is_updatable() against overly large attnums","url":"/m/pgsql-committers/E1xTlyC-00000000I0e-43Rc@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"drowley@postgresql.org","name":"David Rowley","person_id":1009301,"role":"author"},{"email":"hackerzheng666@gmail.com","name":"Zheng Hacker","person_id":26873974,"role":"reported-by"}],"subject":"Robustify pg_column_is_updatable() against overly large attnums"},{"author":"David Rowley","commit":"3a95588fef072ab22aa276d14065ad1bf6bcc976","date":"2026-11-18T20:01:04Z","email":"drowley@postgresql.org","id":"01M7R3Z8005ASGFQW6FZY2PJHY","mail_refs":[{"date":"2026-11-15T04:48:38Z","from":"PG Bug reporting form <noreply@postgresql.org>","how_it_refers":"discussion-trailer","inbox":"pgsql-bugs","message_id":"19904-57a44a8aa7638ae4@postgresql.org","subject":"BUG #19904: pg_column_is_updatable(): \"negative bitmapset member not allowed\" for large attnum (int16 overflow)","url":"/m/pgsql-bugs/19904-57a44a8aa7638ae4@postgresql.org/"},{"date":"2026-11-18T20:09:21Z","from":"David Rowley <drowley@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTly4-00000000Hzy-0kkg@gemulon.postgresql.org","subject":"pgsql: Robustify pg_column_is_updatable() against overly large attnums","url":"/m/pgsql-committers/E1xTly4-00000000Hzy-0kkg@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"drowley@postgresql.org","name":"David Rowley","person_id":1009301,"role":"author"},{"email":"hackerzheng666@gmail.com","name":"Zheng Hacker","person_id":26873974,"role":"reported-by"}],"subject":"Robustify pg_column_is_updatable() against overly large attnums"},{"author":"David Rowley","commit":"5f4f6e412ff3ade6660de8126c03d801c6c9de5b","date":"2026-11-18T20:01:04Z","email":"drowley@postgresql.org","id":"01M7R3Z800BHX3K739C0AK2T0B","mail_refs":[{"date":"2026-11-15T04:48:38Z","from":"PG Bug reporting form <noreply@postgresql.org>","how_it_refers":"discussion-trailer","inbox":"pgsql-bugs","message_id":"19904-57a44a8aa7638ae4@postgresql.org","subject":"BUG #19904: pg_column_is_updatable(): \"negative bitmapset member not allowed\" for large attnum (int16 overflow)","url":"/m/pgsql-bugs/19904-57a44a8aa7638ae4@postgresql.org/"},{"date":"2026-11-18T20:09:10Z","from":"David Rowley <drowley@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTlxt-00000000HzK-146v@gemulon.postgresql.org","subject":"pgsql: Robustify pg_column_is_updatable() against overly large attnums","url":"/m/pgsql-committers/E1xTlxt-00000000HzK-146v@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"drowley@postgresql.org","name":"David Rowley","person_id":1009301,"role":"author"},{"email":"hackerzheng666@gmail.com","name":"Zheng Hacker","person_id":26873974,"role":"reported-by"}],"subject":"Robustify pg_column_is_updatable() against overly large attnums"},{"author":"David Rowley","commit":"4892c9447e315f00be028d90a60e1e0ccfe3992d","date":"2026-11-18T20:01:04Z","email":"drowley@postgresql.org","id":"01M7R3Z800JBTFX93CTADG8NH7","mail_refs":[{"date":"2026-11-15T04:48:38Z","from":"PG Bug reporting form <noreply@postgresql.org>","how_it_refers":"discussion-trailer","inbox":"pgsql-bugs","message_id":"19904-57a44a8aa7638ae4@postgresql.org","subject":"BUG #19904: pg_column_is_updatable(): \"negative bitmapset member not allowed\" for large attnum (int16 overflow)","url":"/m/pgsql-bugs/19904-57a44a8aa7638ae4@postgresql.org/"},{"date":"2026-11-18T20:08:57Z","from":"David Rowley <drowley@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTlxg-00000000Hyf-3EVr@gemulon.postgresql.org","subject":"pgsql: Robustify pg_column_is_updatable() against overly large attnums","url":"/m/pgsql-committers/E1xTlxg-00000000Hyf-3EVr@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"drowley@postgresql.org","name":"David Rowley","person_id":1009301,"role":"author"},{"email":"hackerzheng666@gmail.com","name":"Zheng Hacker","person_id":26873974,"role":"reported-by"}],"subject":"Robustify pg_column_is_updatable() against overly large attnums"},{"author":"David Rowley","commit":"8d7914fa68eaf6bc65cc64b4bf668721763d468c","date":"2026-11-18T20:01:04Z","email":"drowley@postgresql.org","id":"01M7R3Z800QD7VR874P3CJQXD6","mail_refs":[{"date":"2026-11-15T04:48:38Z","from":"PG Bug reporting form <noreply@postgresql.org>","how_it_refers":"discussion-trailer","inbox":"pgsql-bugs","message_id":"19904-57a44a8aa7638ae4@postgresql.org","subject":"BUG #19904: pg_column_is_updatable(): \"negative bitmapset member not allowed\" for large attnum (int16 overflow)","url":"/m/pgsql-bugs/19904-57a44a8aa7638ae4@postgresql.org/"},{"date":"2026-11-18T20:09:52Z","from":"David Rowley <drowley@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTlyZ-00000000I1y-0zSk@gemulon.postgresql.org","subject":"pgsql: Robustify pg_column_is_updatable() against overly large attnums","url":"/m/pgsql-committers/E1xTlyZ-00000000I1y-0zSk@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"drowley@postgresql.org","name":"David Rowley","person_id":1009301,"role":"author"},{"email":"hackerzheng666@gmail.com","name":"Zheng Hacker","person_id":26873974,"role":"reported-by"}],"subject":"Robustify pg_column_is_updatable() against overly large attnums"},{"author":"Masahiko Sawada","commit":"597d5c1fef84855254bdc93ebfa612beff889006","date":"2026-11-18T18:57:48Z","email":"msawada@postgresql.org","id":"01M7R0BCZ018JZQAZ3W8XX4SVV","mail_refs":[{"date":"2026-10-23T17:54:28Z","from":"Baji Shaik <baji.pgdev@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com","subject":"[PATCH] Fall back to serializing when parallel apply runs out of DSM segments","url":"/m/pgsql-hackers/CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com/"},{"date":"2026-11-18T18:59:08Z","from":"Masahiko Sawada <msawada@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTks7-00000000HcQ-07mz@gemulon.postgresql.org","subject":"pgsql: Fix DSA allocation to honor DSA_ALLOC_NO_OOM when out of DSM seg","url":"/m/pgsql-committers/E1xTks7-00000000HcQ-07mz@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"msawada@postgresql.org","name":"Masahiko Sawada","person_id":1007301,"role":"author"},{"email":"baji.pgdev@gmail.com","name":"Baji Shaik","person_id":25294189,"role":"author"},{"email":"houzhijie22@gmail.com","name":"Zhijie Hou","person_id":1005701,"role":"reviewed-by"},{"email":"bharath.rupireddyforpostgres@gmail.com","name":"Bharath Rupireddy","person_id":1014501,"role":"reviewed-by"},{"email":"sawada.mshk@gmail.com","name":"Masahiko Sawada","person_id":1007301,"role":"reviewed-by"}],"subject":"Fix DSA allocation to honor DSA_ALLOC_NO_OOM when out of DSM segments."},{"author":"Masahiko Sawada","commit":"91bdcd71baea2ff5a83cc15b3bde4b98a0bd09eb","date":"2026-11-18T18:57:45Z","email":"msawada@postgresql.org","id":"01M7R0BA18AQNP45KZ1WVCAHW8","mail_refs":[{"date":"2026-10-23T17:54:28Z","from":"Baji Shaik <baji.pgdev@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com","subject":"[PATCH] Fall back to serializing when parallel apply runs out of DSM segments","url":"/m/pgsql-hackers/CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com/"},{"date":"2026-11-18T18:59:01Z","from":"Masahiko Sawada <msawada@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTks0-00000000Hbk-3oqt@gemulon.postgresql.org","subject":"pgsql: Fix DSA allocation to honor DSA_ALLOC_NO_OOM when out of DSM seg","url":"/m/pgsql-committers/E1xTks0-00000000Hbk-3oqt@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"msawada@postgresql.org","name":"Masahiko Sawada","person_id":1007301,"role":"author"},{"email":"baji.pgdev@gmail.com","name":"Baji Shaik","person_id":25294189,"role":"author"},{"email":"houzhijie22@gmail.com","name":"Zhijie Hou","person_id":1005701,"role":"reviewed-by"},{"email":"bharath.rupireddyforpostgres@gmail.com","name":"Bharath Rupireddy","person_id":1014501,"role":"reviewed-by"},{"email":"sawada.mshk@gmail.com","name":"Masahiko Sawada","person_id":1007301,"role":"reviewed-by"}],"subject":"Fix DSA allocation to honor DSA_ALLOC_NO_OOM when out of DSM segments."},{"author":"Masahiko Sawada","commit":"d3332adf931e178cbed1d5ab33f8117eee95987a","date":"2026-11-18T18:57:43Z","email":"msawada@postgresql.org","id":"01M7R0B82RRET8F1WZHK4WWC0Z","mail_refs":[{"date":"2026-10-23T17:54:28Z","from":"Baji Shaik <baji.pgdev@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com","subject":"[PATCH] Fall back to serializing when parallel apply runs out of DSM segments","url":"/m/pgsql-hackers/CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com/"},{"date":"2026-11-18T18:58:58Z","from":"Masahiko Sawada <msawada@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkrx-00000000Hb8-12aU@gemulon.postgresql.org","subject":"pgsql: Fix DSA allocation to honor DSA_ALLOC_NO_OOM when out of DSM seg","url":"/m/pgsql-committers/E1xTkrx-00000000Hb8-12aU@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"msawada@postgresql.org","name":"Masahiko Sawada","person_id":1007301,"role":"author"},{"email":"baji.pgdev@gmail.com","name":"Baji Shaik","person_id":25294189,"role":"author"},{"email":"houzhijie22@gmail.com","name":"Zhijie Hou","person_id":1005701,"role":"reviewed-by"},{"email":"bharath.rupireddyforpostgres@gmail.com","name":"Bharath Rupireddy","person_id":1014501,"role":"reviewed-by"},{"email":"sawada.mshk@gmail.com","name":"Masahiko Sawada","person_id":1007301,"role":"reviewed-by"}],"subject":"Fix DSA allocation to honor DSA_ALLOC_NO_OOM when out of DSM segments."},{"author":"Masahiko Sawada","commit":"e3b7f6156916c2ffefb51c12a0576d8b095d5c26","date":"2026-11-18T18:57:40Z","email":"msawada@postgresql.org","id":"01M7R0B550VKG5JJJWKRFXY7C9","mail_refs":[{"date":"2026-10-23T17:54:28Z","from":"Baji Shaik <baji.pgdev@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com","subject":"[PATCH] Fall back to serializing when parallel apply runs out of DSM segments","url":"/m/pgsql-hackers/CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com/"},{"date":"2026-11-18T18:58:54Z","from":"Masahiko Sawada <msawada@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkrt-00000000HaW-2q4y@gemulon.postgresql.org","subject":"pgsql: Fix DSA allocation to honor DSA_ALLOC_NO_OOM when out of DSM seg","url":"/m/pgsql-committers/E1xTkrt-00000000HaW-2q4y@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"msawada@postgresql.org","name":"Masahiko Sawada","person_id":1007301,"role":"author"},{"email":"baji.pgdev@gmail.com","name":"Baji Shaik","person_id":25294189,"role":"author"},{"email":"houzhijie22@gmail.com","name":"Zhijie Hou","person_id":1005701,"role":"reviewed-by"},{"email":"bharath.rupireddyforpostgres@gmail.com","name":"Bharath Rupireddy","person_id":1014501,"role":"reviewed-by"},{"email":"sawada.mshk@gmail.com","name":"Masahiko Sawada","person_id":1007301,"role":"reviewed-by"}],"subject":"Fix DSA allocation to honor DSA_ALLOC_NO_OOM when out of DSM segments."},{"author":"Masahiko Sawada","commit":"1eb1e8b5f366b78d5a0e3821c3a197b7ab0f6ea4","date":"2026-11-18T18:57:37Z","email":"msawada@postgresql.org","id":"01M7R0B278F36SJX51V9VZQG5Y","mail_refs":[{"date":"2026-10-23T17:54:28Z","from":"Baji Shaik <baji.pgdev@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com","subject":"[PATCH] Fall back to serializing when parallel apply runs out of DSM segments","url":"/m/pgsql-hackers/CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com/"},{"date":"2026-11-18T18:58:51Z","from":"Masahiko Sawada <msawada@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkrq-00000000HZu-09sM@gemulon.postgresql.org","subject":"pgsql: Fix DSA allocation to honor DSA_ALLOC_NO_OOM when out of DSM seg","url":"/m/pgsql-committers/E1xTkrq-00000000HZu-09sM@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"msawada@postgresql.org","name":"Masahiko Sawada","person_id":1007301,"role":"author"},{"email":"baji.pgdev@gmail.com","name":"Baji Shaik","person_id":25294189,"role":"author"},{"email":"houzhijie22@gmail.com","name":"Zhijie Hou","person_id":1005701,"role":"reviewed-by"},{"email":"bharath.rupireddyforpostgres@gmail.com","name":"Bharath Rupireddy","person_id":1014501,"role":"reviewed-by"},{"email":"sawada.mshk@gmail.com","name":"Masahiko Sawada","person_id":1007301,"role":"reviewed-by"}],"subject":"Fix DSA allocation to honor DSA_ALLOC_NO_OOM when out of DSM segments."},{"author":"Masahiko Sawada","commit":"19ab0bae3aa3c006503da10e6e250d6e5529394c","date":"2026-11-18T18:57:34Z","email":"msawada@postgresql.org","id":"01M7R0AZ9GW3X3JDRYPP7MQ1B4","mail_refs":[{"date":"2026-10-23T17:54:28Z","from":"Baji Shaik <baji.pgdev@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com","subject":"[PATCH] Fall back to serializing when parallel apply runs out of DSM segments","url":"/m/pgsql-hackers/CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com/"},{"date":"2026-11-18T18:58:47Z","from":"Masahiko Sawada <msawada@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkrm-00000000HZG-1vhf@gemulon.postgresql.org","subject":"pgsql: Fix DSA allocation to honor DSA_ALLOC_NO_OOM when out of DSM seg","url":"/m/pgsql-committers/E1xTkrm-00000000HZG-1vhf@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"msawada@postgresql.org","name":"Masahiko Sawada","person_id":1007301,"role":"author"},{"email":"baji.pgdev@gmail.com","name":"Baji Shaik","person_id":25294189,"role":"author"},{"email":"houzhijie22@gmail.com","name":"Zhijie Hou","person_id":1005701,"role":"reviewed-by"},{"email":"bharath.rupireddyforpostgres@gmail.com","name":"Bharath Rupireddy","person_id":1014501,"role":"reviewed-by"},{"email":"sawada.mshk@gmail.com","name":"Masahiko Sawada","person_id":1007301,"role":"reviewed-by"}],"subject":"Fix DSA allocation to honor DSA_ALLOC_NO_OOM when out of DSM segments."},{"author":"Melanie Plageman","commit":"1e88ed142938926d8b0513350f7c2b0aa5616095","date":"2026-11-18T18:30:32Z","email":"melanieplageman@gmail.com","id":"01M7QYSFA0Q1KRDE7XXG2VN18Y","mail_refs":[{"date":"2026-11-18T18:55:24Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkoV-00000000HSS-48Hv@gemulon.postgresql.org","subject":"pgsql: Fix pgstattuple test with forced parallel queries","url":"/m/pgsql-committers/E1xTkoV-00000000HSS-48Hv@gemulon.postgresql.org/"}],"mail_refs_total":1,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"}],"subject":"Fix pgstattuple test with forced parallel queries"},{"author":"Melanie Plageman","commit":"ce889ae89d0ddb51c0b12c8cd42e9aa792f29c9e","date":"2026-11-18T18:30:32Z","email":"melanieplageman@gmail.com","id":"01M7QYSFA0APH4ME084B26ZQYF","mail_refs":[{"date":"2026-11-18T18:50:21Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkjc-00000000HMp-2IME@gemulon.postgresql.org","subject":"pgsql: Fix pgstattuple test with forced parallel queries","url":"/m/pgsql-committers/E1xTkjc-00000000HMp-2IME@gemulon.postgresql.org/"}],"mail_refs_total":1,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"}],"subject":"Fix pgstattuple test with forced parallel queries"},{"author":"Melanie Plageman","commit":"1a7874fe4fe17c4d3a90586e7d84c4a75982fb29","date":"2026-11-18T18:30:32Z","email":"melanieplageman@gmail.com","id":"01M7QYSFA0B3Q90T24Q3VF4AD6","mail_refs":[{"date":"2026-11-18T18:49:34Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkir-00000000HM6-2av1@gemulon.postgresql.org","subject":"pgsql: Fix pgstattuple test with forced parallel queries","url":"/m/pgsql-committers/E1xTkir-00000000HM6-2av1@gemulon.postgresql.org/"}],"mail_refs_total":1,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"}],"subject":"Fix pgstattuple test with forced parallel queries"},{"author":"Melanie Plageman","commit":"e406b97cfd88143773fc52b56c7c4f83183d25d1","date":"2026-11-18T18:30:32Z","email":"melanieplageman@gmail.com","id":"01M7QYSFA0NQBPZAFEB9FGB6VP","mail_refs":[{"date":"2026-11-18T18:51:03Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkkI-00000000HNe-3Gh0@gemulon.postgresql.org","subject":"pgsql: Fix pgstattuple test with forced parallel queries","url":"/m/pgsql-committers/E1xTkkI-00000000HNe-3Gh0@gemulon.postgresql.org/"}],"mail_refs_total":1,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"}],"subject":"Fix pgstattuple test with forced parallel queries"},{"author":"Melanie Plageman","commit":"bf71c81380f06a5c05f3f104a52c21a67a03631a","date":"2026-11-18T18:30:32Z","email":"melanieplageman@gmail.com","id":"01M7QYSFA0XR469KBN1JXV1V51","mail_refs":[{"date":"2026-11-18T18:47:45Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkh6-00000000HLI-1n6O@gemulon.postgresql.org","subject":"pgsql: Fix pgstattuple test with forced parallel queries","url":"/m/pgsql-committers/E1xTkh6-00000000HLI-1n6O@gemulon.postgresql.org/"}],"mail_refs_total":1,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"}],"subject":"Fix pgstattuple test with forced parallel queries"},{"author":"Melanie Plageman","commit":"5861eabe38123fca1f00a7b9ae63810cae4054f1","date":"2026-11-18T18:30:32Z","email":"melanieplageman@gmail.com","id":"01M7QYSFA0N887HSZ5P26PXPJT","mail_refs":[{"date":"2026-11-18T18:46:58Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkgL-00000000HJj-1ZD4@gemulon.postgresql.org","subject":"pgsql: Fix pgstattuple test with forced parallel queries","url":"/m/pgsql-committers/E1xTkgL-00000000HJj-1ZD4@gemulon.postgresql.org/"}],"mail_refs_total":1,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"}],"subject":"Fix pgstattuple test with forced parallel queries"},{"author":"Masahiko Sawada","commit":"5aafc5cb6ee2747cf76fa60804ca248c833039f4","date":"2026-11-18T18:29:46Z","email":"msawada@postgresql.org","id":"01M7QYR2CG76YTZ2FVBF0F74JJ","mail_refs":[{"date":"2026-10-23T17:54:28Z","from":"Baji Shaik <baji.pgdev@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com","subject":"[PATCH] Fall back to serializing when parallel apply runs out of DSM segments","url":"/m/pgsql-hackers/CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com/"},{"date":"2026-11-18T18:30:45Z","from":"Masahiko Sawada <msawada@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkQe-00000000HDF-3Ee0@gemulon.postgresql.org","subject":"pgsql: Fall back to serializing when parallel apply runs out of DSM seg","url":"/m/pgsql-committers/E1xTkQe-00000000HDF-3Ee0@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"msawada@postgresql.org","name":"Masahiko Sawada","person_id":1007301,"role":"author"},{"email":"baji.pgdev@gmail.com","name":"Baji Shaik","person_id":25294189,"role":"author"},{"email":"houzhijie22@gmail.com","name":"Zhijie Hou","person_id":1005701,"role":"reviewed-by"},{"email":"bharath.rupireddyforpostgres@gmail.com","name":"Bharath Rupireddy","person_id":1014501,"role":"reviewed-by"},{"email":"sawada.mshk@gmail.com","name":"Masahiko Sawada","person_id":1007301,"role":"reviewed-by"}],"subject":"Fall back to serializing when parallel apply runs out of DSM segments."},{"author":"Masahiko Sawada","commit":"083f30f4763c60013b6f90deb3d4ee57bbf03db4","date":"2026-11-18T18:29:44Z","email":"msawada@postgresql.org","id":"01M7QYR0E0590GGVZ0ZT3421CX","mail_refs":[{"date":"2026-10-23T17:54:28Z","from":"Baji Shaik <baji.pgdev@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com","subject":"[PATCH] Fall back to serializing when parallel apply runs out of DSM segments","url":"/m/pgsql-hackers/CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com/"},{"date":"2026-11-18T18:30:41Z","from":"Masahiko Sawada <msawada@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkQa-00000000HCd-3aDB@gemulon.postgresql.org","subject":"pgsql: Fall back to serializing when parallel apply runs out of DSM seg","url":"/m/pgsql-committers/E1xTkQa-00000000HCd-3aDB@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"msawada@postgresql.org","name":"Masahiko Sawada","person_id":1007301,"role":"author"},{"email":"baji.pgdev@gmail.com","name":"Baji Shaik","person_id":25294189,"role":"author"},{"email":"houzhijie22@gmail.com","name":"Zhijie Hou","person_id":1005701,"role":"reviewed-by"},{"email":"bharath.rupireddyforpostgres@gmail.com","name":"Bharath Rupireddy","person_id":1014501,"role":"reviewed-by"},{"email":"sawada.mshk@gmail.com","name":"Masahiko Sawada","person_id":1007301,"role":"reviewed-by"}],"subject":"Fall back to serializing when parallel apply runs out of DSM segments."},{"author":"Masahiko Sawada","commit":"3b367aaa57a35d8561972cb777ca2227c1547c63","date":"2026-11-18T18:29:41Z","email":"msawada@postgresql.org","id":"01M7QYQXG8NYMRXQMW1RJRXGTJ","mail_refs":[{"date":"2026-10-23T17:54:28Z","from":"Baji Shaik <baji.pgdev@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com","subject":"[PATCH] Fall back to serializing when parallel apply runs out of DSM segments","url":"/m/pgsql-hackers/CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com/"},{"date":"2026-11-18T18:30:37Z","from":"Masahiko Sawada <msawada@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkQW-00000000HBz-2uRm@gemulon.postgresql.org","subject":"pgsql: Fall back to serializing when parallel apply runs out of DSM seg","url":"/m/pgsql-committers/E1xTkQW-00000000HBz-2uRm@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"msawada@postgresql.org","name":"Masahiko Sawada","person_id":1007301,"role":"author"},{"email":"baji.pgdev@gmail.com","name":"Baji Shaik","person_id":25294189,"role":"author"},{"email":"houzhijie22@gmail.com","name":"Zhijie Hou","person_id":1005701,"role":"reviewed-by"},{"email":"bharath.rupireddyforpostgres@gmail.com","name":"Bharath Rupireddy","person_id":1014501,"role":"reviewed-by"},{"email":"sawada.mshk@gmail.com","name":"Masahiko Sawada","person_id":1007301,"role":"reviewed-by"}],"subject":"Fall back to serializing when parallel apply runs out of DSM segments."},{"author":"Masahiko Sawada","commit":"f22cb79d05b0a9dfc9b4065a8f8f08c4c716fd2d","date":"2026-11-18T18:29:38Z","email":"msawada@postgresql.org","id":"01M7QYQTJGR22P7ZVAFT4093RH","mail_refs":[{"date":"2026-10-23T17:54:28Z","from":"Baji Shaik <baji.pgdev@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com","subject":"[PATCH] Fall back to serializing when parallel apply runs out of DSM segments","url":"/m/pgsql-hackers/CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com/"},{"date":"2026-11-18T18:30:33Z","from":"Masahiko Sawada <msawada@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkQS-00000000HBM-1FB0@gemulon.postgresql.org","subject":"pgsql: Fall back to serializing when parallel apply runs out of DSM seg","url":"/m/pgsql-committers/E1xTkQS-00000000HBM-1FB0@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"msawada@postgresql.org","name":"Masahiko Sawada","person_id":1007301,"role":"author"},{"email":"baji.pgdev@gmail.com","name":"Baji Shaik","person_id":25294189,"role":"author"},{"email":"houzhijie22@gmail.com","name":"Zhijie Hou","person_id":1005701,"role":"reviewed-by"},{"email":"bharath.rupireddyforpostgres@gmail.com","name":"Bharath Rupireddy","person_id":1014501,"role":"reviewed-by"},{"email":"sawada.mshk@gmail.com","name":"Masahiko Sawada","person_id":1007301,"role":"reviewed-by"}],"subject":"Fall back to serializing when parallel apply runs out of DSM segments."},{"author":"Masahiko Sawada","commit":"c790e38b4a26f8546a10f3a4fdb79cf090f70632","date":"2026-11-18T18:29:35Z","email":"msawada@postgresql.org","id":"01M7QYQQMRY299GC50AFBCDSEN","mail_refs":[{"date":"2026-10-23T17:54:28Z","from":"Baji Shaik <baji.pgdev@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com","subject":"[PATCH] Fall back to serializing when parallel apply runs out of DSM segments","url":"/m/pgsql-hackers/CA+fm-RMyb6EoMuk+a4_hZou9cdTHfB6mj1UV-7yb_YuTWLug1g@mail.gmail.com/"},{"date":"2026-11-18T18:30:29Z","from":"Masahiko Sawada <msawada@postgresql.org>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTkQO-00000000HAi-1pOi@gemulon.postgresql.org","subject":"pgsql: Fall back to serializing when parallel apply runs out of DSM seg","url":"/m/pgsql-committers/E1xTkQO-00000000HAi-1pOi@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"msawada@postgresql.org","name":"Masahiko Sawada","person_id":1007301,"role":"author"},{"email":"baji.pgdev@gmail.com","name":"Baji Shaik","person_id":25294189,"role":"author"},{"email":"houzhijie22@gmail.com","name":"Zhijie Hou","person_id":1005701,"role":"reviewed-by"},{"email":"bharath.rupireddyforpostgres@gmail.com","name":"Bharath Rupireddy","person_id":1014501,"role":"reviewed-by"},{"email":"sawada.mshk@gmail.com","name":"Masahiko Sawada","person_id":1007301,"role":"reviewed-by"}],"subject":"Fall back to serializing when parallel apply runs out of DSM segments."},{"author":"Tom Lane","commit":"68b927397e7641432078b2fcfa8f1f5f60a9a42d","date":"2026-11-18T17:45:28Z","email":"tgl@sss.pgh.pa.us","id":"01M7QW6YP097FGXP3Y6PM6P62T","mail_refs":[{"date":"2026-11-13T16:20:52Z","from":"韩建桥 <hanjianqiao@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAPOa_Zkc1QROJwB_JcB+f=6s1bUPRh7qr_H_=B_S-KZPa0V1DA@mail.gmail.com","subject":"[PATCH] Normalize numeric/bigint scientific notation after rounding","url":"/m/pgsql-hackers/CAPOa_Zkc1QROJwB_JcB+f=6s1bUPRh7qr_H_=B_S-KZPa0V1DA@mail.gmail.com/"},{"date":"2026-11-18T17:45:44Z","from":"Tom Lane <tgl@sss.pgh.pa.us>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTjj5-00000000GtP-2pHV@gemulon.postgresql.org","subject":"pgsql: Fix formatting of to_char's EEEE output for numeric and bigint.","url":"/m/pgsql-committers/E1xTjj5-00000000GtP-2pHV@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"tgl@sss.pgh.pa.us","name":"Tom Lane","person_id":1003301,"role":"author"},{"email":"hanjianqiao@gmail.com","name":"Jianqiao Han","person_id":null,"role":"author"}],"subject":"Fix formatting of to_char's EEEE output for numeric and bigint."},{"author":"Tom Lane","commit":"a355dde4df2b6360bbe1292c22061e948d9d0ee0","date":"2026-11-18T17:45:28Z","email":"tgl@sss.pgh.pa.us","id":"01M7QW6YP01JGFHFGJVED6945G","mail_refs":[{"date":"2026-11-13T16:20:52Z","from":"韩建桥 <hanjianqiao@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAPOa_Zkc1QROJwB_JcB+f=6s1bUPRh7qr_H_=B_S-KZPa0V1DA@mail.gmail.com","subject":"[PATCH] Normalize numeric/bigint scientific notation after rounding","url":"/m/pgsql-hackers/CAPOa_Zkc1QROJwB_JcB+f=6s1bUPRh7qr_H_=B_S-KZPa0V1DA@mail.gmail.com/"},{"date":"2026-11-18T17:45:44Z","from":"Tom Lane <tgl@sss.pgh.pa.us>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTjj5-00000000Gtb-3Knv@gemulon.postgresql.org","subject":"pgsql: Fix formatting of to_char's EEEE output for numeric and bigint.","url":"/m/pgsql-committers/E1xTjj5-00000000Gtb-3Knv@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"tgl@sss.pgh.pa.us","name":"Tom Lane","person_id":1003301,"role":"author"},{"email":"hanjianqiao@gmail.com","name":"Jianqiao Han","person_id":null,"role":"author"}],"subject":"Fix formatting of to_char's EEEE output for numeric and bigint."},{"author":"Tom Lane","commit":"a9e88fab7f0188af4f0bc0e4b656cf23d79ff2da","date":"2026-11-18T17:45:28Z","email":"tgl@sss.pgh.pa.us","id":"01M7QW6YP0AGTH4WGSFDMSKQ4Y","mail_refs":[{"date":"2026-11-13T16:20:52Z","from":"韩建桥 <hanjianqiao@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAPOa_Zkc1QROJwB_JcB+f=6s1bUPRh7qr_H_=B_S-KZPa0V1DA@mail.gmail.com","subject":"[PATCH] Normalize numeric/bigint scientific notation after rounding","url":"/m/pgsql-hackers/CAPOa_Zkc1QROJwB_JcB+f=6s1bUPRh7qr_H_=B_S-KZPa0V1DA@mail.gmail.com/"},{"date":"2026-11-18T17:45:44Z","from":"Tom Lane <tgl@sss.pgh.pa.us>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTjj5-00000000GtY-3Cuk@gemulon.postgresql.org","subject":"pgsql: Fix formatting of to_char's EEEE output for numeric and bigint.","url":"/m/pgsql-committers/E1xTjj5-00000000GtY-3Cuk@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"tgl@sss.pgh.pa.us","name":"Tom Lane","person_id":1003301,"role":"author"},{"email":"hanjianqiao@gmail.com","name":"Jianqiao Han","person_id":null,"role":"author"}],"subject":"Fix formatting of to_char's EEEE output for numeric and bigint."},{"author":"Tom Lane","commit":"4751b0490ea4965dab302b1c8e7ac7db9be3f466","date":"2026-11-18T17:45:28Z","email":"tgl@sss.pgh.pa.us","id":"01M7QW6YP0DZR1Q2Y7VYBES50H","mail_refs":[{"date":"2026-11-13T16:20:52Z","from":"韩建桥 <hanjianqiao@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAPOa_Zkc1QROJwB_JcB+f=6s1bUPRh7qr_H_=B_S-KZPa0V1DA@mail.gmail.com","subject":"[PATCH] Normalize numeric/bigint scientific notation after rounding","url":"/m/pgsql-hackers/CAPOa_Zkc1QROJwB_JcB+f=6s1bUPRh7qr_H_=B_S-KZPa0V1DA@mail.gmail.com/"},{"date":"2026-11-18T17:45:44Z","from":"Tom Lane <tgl@sss.pgh.pa.us>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTjj5-00000000GtW-34lR@gemulon.postgresql.org","subject":"pgsql: Fix formatting of to_char's EEEE output for numeric and bigint.","url":"/m/pgsql-committers/E1xTjj5-00000000GtW-34lR@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"tgl@sss.pgh.pa.us","name":"Tom Lane","person_id":1003301,"role":"author"},{"email":"hanjianqiao@gmail.com","name":"Jianqiao Han","person_id":null,"role":"author"}],"subject":"Fix formatting of to_char's EEEE output for numeric and bigint."},{"author":"Tom Lane","commit":"cdd975becc5f378269e1d5bec71c2804d775ccab","date":"2026-11-18T17:45:28Z","email":"tgl@sss.pgh.pa.us","id":"01M7QW6YP0SSEV8Z3FMBZ6NFGZ","mail_refs":[{"date":"2026-11-13T16:20:52Z","from":"韩建桥 <hanjianqiao@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAPOa_Zkc1QROJwB_JcB+f=6s1bUPRh7qr_H_=B_S-KZPa0V1DA@mail.gmail.com","subject":"[PATCH] Normalize numeric/bigint scientific notation after rounding","url":"/m/pgsql-hackers/CAPOa_Zkc1QROJwB_JcB+f=6s1bUPRh7qr_H_=B_S-KZPa0V1DA@mail.gmail.com/"},{"date":"2026-11-18T17:45:44Z","from":"Tom Lane <tgl@sss.pgh.pa.us>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTjj5-00000000GtT-30si@gemulon.postgresql.org","subject":"pgsql: Fix formatting of to_char's EEEE output for numeric and bigint.","url":"/m/pgsql-committers/E1xTjj5-00000000GtT-30si@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"tgl@sss.pgh.pa.us","name":"Tom Lane","person_id":1003301,"role":"author"},{"email":"hanjianqiao@gmail.com","name":"Jianqiao Han","person_id":null,"role":"author"}],"subject":"Fix formatting of to_char's EEEE output for numeric and bigint."},{"author":"Tom Lane","commit":"e56e83211f44703d5e03b00f8e66e777d2d5fdbd","date":"2026-11-18T17:45:28Z","email":"tgl@sss.pgh.pa.us","id":"01M7QW6YP0SJQHHFNBM2E94753","mail_refs":[{"date":"2026-11-13T16:20:52Z","from":"韩建桥 <hanjianqiao@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAPOa_Zkc1QROJwB_JcB+f=6s1bUPRh7qr_H_=B_S-KZPa0V1DA@mail.gmail.com","subject":"[PATCH] Normalize numeric/bigint scientific notation after rounding","url":"/m/pgsql-hackers/CAPOa_Zkc1QROJwB_JcB+f=6s1bUPRh7qr_H_=B_S-KZPa0V1DA@mail.gmail.com/"},{"date":"2026-11-18T17:45:44Z","from":"Tom Lane <tgl@sss.pgh.pa.us>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTjj5-00000000GtR-2uBu@gemulon.postgresql.org","subject":"pgsql: Fix formatting of to_char's EEEE output for numeric and bigint.","url":"/m/pgsql-committers/E1xTjj5-00000000GtR-2uBu@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"tgl@sss.pgh.pa.us","name":"Tom Lane","person_id":1003301,"role":"author"},{"email":"hanjianqiao@gmail.com","name":"Jianqiao Han","person_id":null,"role":"author"}],"subject":"Fix formatting of to_char's EEEE output for numeric and bigint."},{"author":"Dean Rasheed","commit":"ea5eb6d62eaa76f5dc90ee2ca8fd0d75b042f809","date":"2026-11-18T16:04:38Z","email":"dean.a.rasheed@gmail.com","id":"01M7QPEAFG6F1DK5J71J6QG729","mail_refs":[{"date":"2026-10-08T22:44:49Z","from":"Michael Ries <mries@salesforce.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-bugs","message_id":"CAKWDHLgETF86qEW40HcEzMgn5DdmS6yR-nSYwemXF7zFGrU+sQ@mail.gmail.com","subject":"Bug in statement trigger for MERGE operations that move rows between partitions","url":"/m/pgsql-bugs/CAKWDHLgETF86qEW40HcEzMgn5DdmS6yR-nSYwemXF7zFGrU+sQ@mail.gmail.com/"},{"date":"2026-11-05T06:47:29Z","from":"Tender Wang <tndrwang@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAHewXNk8MgaFMD87s=xHeguzmErEjsqeroxrMyQbKyXwG5eocw@mail.gmail.com","subject":"MERGE loses UPDATE transition rows when moving rows between partitions","url":"/m/pgsql-hackers/CAHewXNk8MgaFMD87s=xHeguzmErEjsqeroxrMyQbKyXwG5eocw@mail.gmail.com/"},{"date":"2026-11-18T16:05:53Z","from":"Dean Rasheed <dean.a.rasheed@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTiAS-00000000GQi-2bT7@gemulon.postgresql.org","subject":"pgsql: Fix transition tables for MERGE with cross-partition UPDATEs.","url":"/m/pgsql-committers/E1xTiAS-00000000GQi-2bT7@gemulon.postgresql.org/"}],"mail_refs_total":3,"people":[{"email":"dean.a.rasheed@gmail.com","name":"Dean Rasheed","person_id":25294341,"role":"author"},{"email":"mries@salesforce.com","name":"Michael Ries","person_id":null,"role":"reported-by"},{"email":"tndrwang@gmail.com","name":"Tender Wang","person_id":25295261,"role":"reported-by"},{"email":"zhong950419@gmail.com","name":"shihao zhong","person_id":25295394,"role":"reviewed-by"}],"subject":"Fix transition tables for MERGE with cross-partition UPDATEs."},{"author":"Dean Rasheed","commit":"46e48c5607e97fcc9cccd38ae3cd96b952dc6bd0","date":"2026-11-18T16:04:37Z","email":"dean.a.rasheed@gmail.com","id":"01M7QPE9G8AT21BRVFEHRRSSP5","mail_refs":[{"date":"2026-10-08T22:44:49Z","from":"Michael Ries <mries@salesforce.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-bugs","message_id":"CAKWDHLgETF86qEW40HcEzMgn5DdmS6yR-nSYwemXF7zFGrU+sQ@mail.gmail.com","subject":"Bug in statement trigger for MERGE operations that move rows between partitions","url":"/m/pgsql-bugs/CAKWDHLgETF86qEW40HcEzMgn5DdmS6yR-nSYwemXF7zFGrU+sQ@mail.gmail.com/"},{"date":"2026-11-05T06:47:29Z","from":"Tender Wang <tndrwang@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAHewXNk8MgaFMD87s=xHeguzmErEjsqeroxrMyQbKyXwG5eocw@mail.gmail.com","subject":"MERGE loses UPDATE transition rows when moving rows between partitions","url":"/m/pgsql-hackers/CAHewXNk8MgaFMD87s=xHeguzmErEjsqeroxrMyQbKyXwG5eocw@mail.gmail.com/"},{"date":"2026-11-18T16:05:53Z","from":"Dean Rasheed <dean.a.rasheed@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTiAS-00000000GQf-2T8I@gemulon.postgresql.org","subject":"pgsql: Fix transition tables for MERGE with cross-partition UPDATEs.","url":"/m/pgsql-committers/E1xTiAS-00000000GQf-2T8I@gemulon.postgresql.org/"}],"mail_refs_total":3,"people":[{"email":"dean.a.rasheed@gmail.com","name":"Dean Rasheed","person_id":25294341,"role":"author"},{"email":"mries@salesforce.com","name":"Michael Ries","person_id":null,"role":"reported-by"},{"email":"tndrwang@gmail.com","name":"Tender Wang","person_id":25295261,"role":"reported-by"},{"email":"zhong950419@gmail.com","name":"shihao zhong","person_id":25295394,"role":"reviewed-by"}],"subject":"Fix transition tables for MERGE with cross-partition UPDATEs."},{"author":"Dean Rasheed","commit":"ff3cdeb9d9ff7c7b8951f981aea5602564a2e031","date":"2026-11-18T16:04:36Z","email":"dean.a.rasheed@gmail.com","id":"01M7QPE8H0V5GTHR6XVZ1175G2","mail_refs":[{"date":"2026-10-08T22:44:49Z","from":"Michael Ries <mries@salesforce.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-bugs","message_id":"CAKWDHLgETF86qEW40HcEzMgn5DdmS6yR-nSYwemXF7zFGrU+sQ@mail.gmail.com","subject":"Bug in statement trigger for MERGE operations that move rows between partitions","url":"/m/pgsql-bugs/CAKWDHLgETF86qEW40HcEzMgn5DdmS6yR-nSYwemXF7zFGrU+sQ@mail.gmail.com/"},{"date":"2026-11-05T06:47:29Z","from":"Tender Wang <tndrwang@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAHewXNk8MgaFMD87s=xHeguzmErEjsqeroxrMyQbKyXwG5eocw@mail.gmail.com","subject":"MERGE loses UPDATE transition rows when moving rows between partitions","url":"/m/pgsql-hackers/CAHewXNk8MgaFMD87s=xHeguzmErEjsqeroxrMyQbKyXwG5eocw@mail.gmail.com/"},{"date":"2026-11-18T16:05:53Z","from":"Dean Rasheed <dean.a.rasheed@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTiAS-00000000GQd-2Irh@gemulon.postgresql.org","subject":"pgsql: Fix transition tables for MERGE with cross-partition UPDATEs.","url":"/m/pgsql-committers/E1xTiAS-00000000GQd-2Irh@gemulon.postgresql.org/"}],"mail_refs_total":3,"people":[{"email":"dean.a.rasheed@gmail.com","name":"Dean Rasheed","person_id":25294341,"role":"author"},{"email":"mries@salesforce.com","name":"Michael Ries","person_id":null,"role":"reported-by"},{"email":"tndrwang@gmail.com","name":"Tender Wang","person_id":25295261,"role":"reported-by"},{"email":"zhong950419@gmail.com","name":"shihao zhong","person_id":25295394,"role":"reviewed-by"}],"subject":"Fix transition tables for MERGE with cross-partition UPDATEs."},{"author":"Dean Rasheed","commit":"84b36063f4092c54f0cc628e6d9c684af6128d07","date":"2026-11-18T16:04:35Z","email":"dean.a.rasheed@gmail.com","id":"01M7QPE7HR2CBK09P6CB8F5H25","mail_refs":[{"date":"2026-10-08T22:44:49Z","from":"Michael Ries <mries@salesforce.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-bugs","message_id":"CAKWDHLgETF86qEW40HcEzMgn5DdmS6yR-nSYwemXF7zFGrU+sQ@mail.gmail.com","subject":"Bug in statement trigger for MERGE operations that move rows between partitions","url":"/m/pgsql-bugs/CAKWDHLgETF86qEW40HcEzMgn5DdmS6yR-nSYwemXF7zFGrU+sQ@mail.gmail.com/"},{"date":"2026-11-05T06:47:29Z","from":"Tender Wang <tndrwang@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAHewXNk8MgaFMD87s=xHeguzmErEjsqeroxrMyQbKyXwG5eocw@mail.gmail.com","subject":"MERGE loses UPDATE transition rows when moving rows between partitions","url":"/m/pgsql-hackers/CAHewXNk8MgaFMD87s=xHeguzmErEjsqeroxrMyQbKyXwG5eocw@mail.gmail.com/"},{"date":"2026-11-18T16:05:53Z","from":"Dean Rasheed <dean.a.rasheed@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTiAS-00000000GQa-2EYT@gemulon.postgresql.org","subject":"pgsql: Fix transition tables for MERGE with cross-partition UPDATEs.","url":"/m/pgsql-committers/E1xTiAS-00000000GQa-2EYT@gemulon.postgresql.org/"}],"mail_refs_total":3,"people":[{"email":"dean.a.rasheed@gmail.com","name":"Dean Rasheed","person_id":25294341,"role":"author"},{"email":"mries@salesforce.com","name":"Michael Ries","person_id":null,"role":"reported-by"},{"email":"tndrwang@gmail.com","name":"Tender Wang","person_id":25295261,"role":"reported-by"},{"email":"zhong950419@gmail.com","name":"shihao zhong","person_id":25295394,"role":"reviewed-by"}],"subject":"Fix transition tables for MERGE with cross-partition UPDATEs."},{"author":"Dean Rasheed","commit":"a1144537703ef7dd12e53de0f30a110c1aa8a35b","date":"2026-11-18T16:04:34Z","email":"dean.a.rasheed@gmail.com","id":"01M7QPE6JGXAGQ6K5J6ZFJ57KP","mail_refs":[{"date":"2026-10-08T22:44:49Z","from":"Michael Ries <mries@salesforce.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-bugs","message_id":"CAKWDHLgETF86qEW40HcEzMgn5DdmS6yR-nSYwemXF7zFGrU+sQ@mail.gmail.com","subject":"Bug in statement trigger for MERGE operations that move rows between partitions","url":"/m/pgsql-bugs/CAKWDHLgETF86qEW40HcEzMgn5DdmS6yR-nSYwemXF7zFGrU+sQ@mail.gmail.com/"},{"date":"2026-11-05T06:47:29Z","from":"Tender Wang <tndrwang@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAHewXNk8MgaFMD87s=xHeguzmErEjsqeroxrMyQbKyXwG5eocw@mail.gmail.com","subject":"MERGE loses UPDATE transition rows when moving rows between partitions","url":"/m/pgsql-hackers/CAHewXNk8MgaFMD87s=xHeguzmErEjsqeroxrMyQbKyXwG5eocw@mail.gmail.com/"},{"date":"2026-11-18T16:05:53Z","from":"Dean Rasheed <dean.a.rasheed@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTiAS-00000000GQY-28FK@gemulon.postgresql.org","subject":"pgsql: Fix transition tables for MERGE with cross-partition UPDATEs.","url":"/m/pgsql-committers/E1xTiAS-00000000GQY-28FK@gemulon.postgresql.org/"}],"mail_refs_total":3,"people":[{"email":"dean.a.rasheed@gmail.com","name":"Dean Rasheed","person_id":25294341,"role":"author"},{"email":"mries@salesforce.com","name":"Michael Ries","person_id":null,"role":"reported-by"},{"email":"tndrwang@gmail.com","name":"Tender Wang","person_id":25295261,"role":"reported-by"},{"email":"zhong950419@gmail.com","name":"shihao zhong","person_id":25295394,"role":"reviewed-by"}],"subject":"Fix transition tables for MERGE with cross-partition UPDATEs."},{"author":"Dean Rasheed","commit":"1e676702cac06e3d51942cc69efc282663515fba","date":"2026-11-18T16:04:33Z","email":"dean.a.rasheed@gmail.com","id":"01M7QPE5K87S4AS23CSBDN06W2","mail_refs":[{"date":"2026-10-08T22:44:49Z","from":"Michael Ries <mries@salesforce.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-bugs","message_id":"CAKWDHLgETF86qEW40HcEzMgn5DdmS6yR-nSYwemXF7zFGrU+sQ@mail.gmail.com","subject":"Bug in statement trigger for MERGE operations that move rows between partitions","url":"/m/pgsql-bugs/CAKWDHLgETF86qEW40HcEzMgn5DdmS6yR-nSYwemXF7zFGrU+sQ@mail.gmail.com/"},{"date":"2026-11-05T06:47:29Z","from":"Tender Wang <tndrwang@gmail.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAHewXNk8MgaFMD87s=xHeguzmErEjsqeroxrMyQbKyXwG5eocw@mail.gmail.com","subject":"MERGE loses UPDATE transition rows when moving rows between partitions","url":"/m/pgsql-hackers/CAHewXNk8MgaFMD87s=xHeguzmErEjsqeroxrMyQbKyXwG5eocw@mail.gmail.com/"},{"date":"2026-11-18T16:05:53Z","from":"Dean Rasheed <dean.a.rasheed@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTiAS-00000000GQW-1zV2@gemulon.postgresql.org","subject":"pgsql: Fix transition tables for MERGE with cross-partition UPDATEs.","url":"/m/pgsql-committers/E1xTiAS-00000000GQW-1zV2@gemulon.postgresql.org/"}],"mail_refs_total":3,"people":[{"email":"dean.a.rasheed@gmail.com","name":"Dean Rasheed","person_id":25294341,"role":"author"},{"email":"mries@salesforce.com","name":"Michael Ries","person_id":null,"role":"reported-by"},{"email":"tndrwang@gmail.com","name":"Tender Wang","person_id":25295261,"role":"reported-by"},{"email":"zhong950419@gmail.com","name":"shihao zhong","person_id":25295394,"role":"reviewed-by"}],"subject":"Fix transition tables for MERGE with cross-partition UPDATEs."},{"author":"Melanie Plageman","commit":"33ac2b000eaba9664c9c8fa7397629ac59c44dc8","date":"2026-11-18T15:39:17Z","email":"melanieplageman@gmail.com","id":"01M7QMZX487FSPY89HAZVV1XM7","mail_refs":[{"date":"2026-11-12T22:51:35Z","from":"Zsolt Parragi <zsolt.parragi@percona.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAN4CZFM0y8t+AQ8PWTeuBXnFtRDUNvkfVzzA_yo6uJ2bceK=xA@mail.gmail.com","subject":"Re: [BUG / PATCH] PG19: VACUUM misestimates reltuples (often 0) after on-access VM setting","url":"/m/pgsql-hackers/CAN4CZFM0y8t+AQ8PWTeuBXnFtRDUNvkfVzzA_yo6uJ2bceK=xA@mail.gmail.com/"},{"date":"2026-11-18T16:02:36Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTi7H-00000000GJx-08ug@gemulon.postgresql.org","subject":"pgsql: Fix pgstattuple_approx handling of unknown tuple estimates","url":"/m/pgsql-committers/E1xTi7H-00000000GJx-08ug@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"},{"email":"zsolt.parragi@percona.com","name":"Zsolt Parragi","person_id":1016701,"role":"reported-by"},{"email":"lukas@fittl.com","name":"Lukas Fittl","person_id":1113501,"role":"reviewed-by"}],"subject":"Fix pgstattuple_approx handling of unknown tuple estimates"},{"author":"Melanie Plageman","commit":"7a733b9547c171e756d2934c77805568ba716ef7","date":"2026-11-18T15:39:17Z","email":"melanieplageman@gmail.com","id":"01M7QMZX482XF0Q8PGCZQRHR5M","mail_refs":[{"date":"2026-11-12T22:51:35Z","from":"Zsolt Parragi <zsolt.parragi@percona.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAN4CZFM0y8t+AQ8PWTeuBXnFtRDUNvkfVzzA_yo6uJ2bceK=xA@mail.gmail.com","subject":"Re: [BUG / PATCH] PG19: VACUUM misestimates reltuples (often 0) after on-access VM setting","url":"/m/pgsql-hackers/CAN4CZFM0y8t+AQ8PWTeuBXnFtRDUNvkfVzzA_yo6uJ2bceK=xA@mail.gmail.com/"},{"date":"2026-11-18T15:58:54Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTi3h-00000000GDB-2q74@gemulon.postgresql.org","subject":"pgsql: Fix pgstattuple_approx handling of unknown tuple estimates","url":"/m/pgsql-committers/E1xTi3h-00000000GDB-2q74@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"},{"email":"zsolt.parragi@percona.com","name":"Zsolt Parragi","person_id":1016701,"role":"reported-by"},{"email":"lukas@fittl.com","name":"Lukas Fittl","person_id":1113501,"role":"reviewed-by"}],"subject":"Fix pgstattuple_approx handling of unknown tuple estimates"},{"author":"Melanie Plageman","commit":"371565fc57f864942baf19520b2983e448e5b0e5","date":"2026-11-18T15:39:17Z","email":"melanieplageman@gmail.com","id":"01M7QMZX48EJYQPM99F4WFNETK","mail_refs":[{"date":"2026-11-12T22:51:35Z","from":"Zsolt Parragi <zsolt.parragi@percona.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAN4CZFM0y8t+AQ8PWTeuBXnFtRDUNvkfVzzA_yo6uJ2bceK=xA@mail.gmail.com","subject":"Re: [BUG / PATCH] PG19: VACUUM misestimates reltuples (often 0) after on-access VM setting","url":"/m/pgsql-hackers/CAN4CZFM0y8t+AQ8PWTeuBXnFtRDUNvkfVzzA_yo6uJ2bceK=xA@mail.gmail.com/"},{"date":"2026-11-18T15:56:28Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xTi1L-00000000G8a-0NMS@gemulon.postgresql.org","subject":"pgsql: Fix pgstattuple_approx handling of unknown tuple estimates","url":"/m/pgsql-committers/E1xTi1L-00000000G8a-0NMS@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"},{"email":"zsolt.parragi@percona.com","name":"Zsolt Parragi","person_id":1016701,"role":"reported-by"},{"email":"lukas@fittl.com","name":"Lukas Fittl","person_id":1113501,"role":"reviewed-by"}],"subject":"Fix pgstattuple_approx handling of unknown tuple estimates"},{"author":"Melanie Plageman","commit":"23a8402f8bdb98cad0baa144ffb7a7d3b4fc7964","date":"2026-11-18T15:39:17Z","email":"melanieplageman@gmail.com","id":"01M7QMZX48ZE64PCN8S4HDX4DV","mail_refs":[{"date":"2026-11-12T22:51:35Z","from":"Zsolt Parragi <zsolt.parragi@percona.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAN4CZFM0y8t+AQ8PWTeuBXnFtRDUNvkfVzzA_yo6uJ2bceK=xA@mail.gmail.com","subject":"Re: [BUG / PATCH] PG19: VACUUM misestimates reltuples (often 0) after on-access VM setting","url":"/m/pgsql-hackers/CAN4CZFM0y8t+AQ8PWTeuBXnFtRDUNvkfVzzA_yo6uJ2bceK=xA@mail.gmail.com/"},{"date":"2026-11-18T15:53:35Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xThyY-00000000G4v-0Mdo@gemulon.postgresql.org","subject":"pgsql: Fix pgstattuple_approx handling of unknown tuple estimates","url":"/m/pgsql-committers/E1xThyY-00000000G4v-0Mdo@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"},{"email":"zsolt.parragi@percona.com","name":"Zsolt Parragi","person_id":1016701,"role":"reported-by"},{"email":"lukas@fittl.com","name":"Lukas Fittl","person_id":1113501,"role":"reviewed-by"}],"subject":"Fix pgstattuple_approx handling of unknown tuple estimates"},{"author":"Melanie Plageman","commit":"ebc86fb8828ba7ef7d164848d990f57d2cf834e5","date":"2026-11-18T15:39:17Z","email":"melanieplageman@gmail.com","id":"01M7QMZX4863VBE7HH9N63QFAE","mail_refs":[{"date":"2026-11-12T22:51:35Z","from":"Zsolt Parragi <zsolt.parragi@percona.com>","how_it_refers":"discussion-trailer","inbox":"pgsql-hackers","message_id":"CAN4CZFM0y8t+AQ8PWTeuBXnFtRDUNvkfVzzA_yo6uJ2bceK=xA@mail.gmail.com","subject":"Re: [BUG / PATCH] PG19: VACUUM misestimates reltuples (often 0) after on-access VM setting","url":"/m/pgsql-hackers/CAN4CZFM0y8t+AQ8PWTeuBXnFtRDUNvkfVzzA_yo6uJ2bceK=xA@mail.gmail.com/"},{"date":"2026-11-18T15:46:12Z","from":"Melanie Plageman <melanieplageman@gmail.com>","how_it_refers":"committers-announcement","inbox":"pgsql-committers","message_id":"E1xThrP-00000000Fyh-3Kfp@gemulon.postgresql.org","subject":"pgsql: Fix pgstattuple_approx handling of unknown tuple estimates","url":"/m/pgsql-committers/E1xThrP-00000000Fyh-3Kfp@gemulon.postgresql.org/"}],"mail_refs_total":2,"people":[{"email":"melanieplageman@gmail.com","name":"Melanie Plageman","person_id":1054701,"role":"author"},{"email":"zsolt.parragi@percona.com","name":"Zsolt Parragi","person_id":1016701,"role":"reported-by"},{"email":"lukas@fittl.com","name":"Lukas Fittl","person_id":1113501,"role":"reviewed-by"}],"subject":"Fix pgstattuple_approx handling of unknown tuple estimates"}],"count":50,"query":"","repo":"postgres"}