pgsql-hackers  

Messages by Thread

• • Re: doc: Document Linux cgroup memory limits Manu
• Re: [Patch] Batch fsyncs when recycling WAL segments Ayush Tiwari
• Partial indexes on system catalogs Manu
  • Re: Partial indexes on system catalogs Andres Freund
  • Re: Partial indexes on system catalogs Tom Lane
  • Re: Partial indexes on system catalogs Manu
  • Re: Partial indexes on system catalogs Manu
• [PATCH] GROUP BY ALL: the regroupening David Christensen
• Re: Improving tracking/processing of buildfarm test failures Alexander Lakhin
• Throwing away unnecessary spin-locks Alexandre Felipe
  • Re: Throwing away unnecessary spin-locks Andres Freund
  • Re: Throwing away unnecessary spin-locks Alexandre Felipe
  • Re: Throwing away unnecessary spin-locks Alexandre Felipe
  • Re: Throwing away unnecessary spin-locks shihao zhong
  • Re: Throwing away unnecessary spin-locks Alexandre Felipe
  • Re: Throwing away unnecessary spin-locks Alexandre Felipe
  • Re: Throwing away unnecessary spin-locks Andres Freund
  • Re: Throwing away unnecessary spin-locks Merlin Moncure
  • Re: Throwing away unnecessary spin-locks Alexandre Felipe
  • Re: Throwing away unnecessary spin-locks Merlin Moncure
  • Re: Throwing away unnecessary spin-locks Andres Freund
  • Re: Throwing away unnecessary spin-locks Alexandre Felipe
• Let an ordering index scan hand its ORDER BY value to the target list Greg Burd
  • Re: Let an ordering index scan hand its ORDER BY value to the target list Greg Burd
  • Re: Let an ordering index scan hand its ORDER BY value to the target list Matthias van de Meent
  • Re: Let an ordering index scan hand its ORDER BY value to the target list Greg Burd
  • Re: Let an ordering index scan hand its ORDER BY value to the target list Greg Burd
  • Re: Let an ordering index scan hand its ORDER BY value to the target list Greg Burd
  • Re: Let an ordering index scan hand its ORDER BY value to the target list Greg Burd
  • Re: Let an ordering index scan hand its ORDER BY value to the target list Matthias van de Meent
  • Re: Let an ordering index scan hand its ORDER BY value to the target list Greg Burd
  • Re: Let an ordering index scan hand its ORDER BY value to the target list Matthias van de Meent
  • Re: Let an ordering index scan hand its ORDER BY value to the target list Greg Burd
  • Re: Let an ordering index scan hand its ORDER BY value to the target list Greg Burd
  • Re: Let an ordering index scan hand its ORDER BY value to the target list Greg Burd
  • Re: Let an ordering index scan hand its ORDER BY value to the target list Oleg Bartunov
  • Re: Let an ordering index scan hand its ORDER BY value to the target list Greg Burd
• Re: Stabilize recovery conflict stats checks in 031_recovery_conflict.pl Alexander Lakhin
  • Re: Stabilize recovery conflict stats checks in 031_recovery_conflict.pl Fujii Masao
• Re: fix more casting away of qualifiers Rui Zhao
  • Re: fix more casting away of qualifiers Peter Eisentraut
  • Re: fix more casting away of qualifiers Andres Freund
  • Re: fix more casting away of qualifiers Peter Eisentraut
  • Re: fix more casting away of qualifiers Rui Zhao
  • Re: fix more casting away of qualifiers Peter Eisentraut
  • Re: fix more casting away of qualifiers Andres Freund
  • Re: fix more casting away of qualifiers Tom Lane
• Re: serializable anomaly - duplicate primary keys Aleksander Alekseev
  • Re: serializable anomaly - duplicate primary keys Aleksander Alekseev
  • Re: serializable anomaly - duplicate primary keys Aleksander Alekseev
  • Re: serializable anomaly - duplicate primary keys Aleksander Alekseev
• CREATE TABLE .. LIKE copies comments to an unrelated table Jim Jones
  • Re: CREATE TABLE .. LIKE copies comments to an unrelated table Junwang Zhao
  • Re: CREATE TABLE .. LIKE copies comments to an unrelated table Jim Jones
  • Re: CREATE TABLE .. LIKE copies comments to an unrelated table Jim Jones
  • Re: CREATE TABLE .. LIKE copies comments to an unrelated table Koshi Shibagaki (Fujitsu)
  • Re: CREATE TABLE .. LIKE copies comments to an unrelated table Jim Jones
  • Re: CREATE TABLE .. LIKE copies comments to an unrelated table Koshi Shibagaki (Fujitsu)
• Re: Report oldest xmin source when autovacuum cannot remove tuples Shinya Kato
  • Re: Report oldest xmin source when autovacuum cannot remove tuples wenhui qiu
  • Re: Report oldest xmin source when autovacuum cannot remove tuples Shinya Kato
• Re: Preserve statistics targets with ALTER TABLE ALTER COLUMN TYPE Zsolt Parragi
  • Re: Preserve statistics targets with ALTER TABLE ALTER COLUMN TYPE solai v
• Wrong LSN in WAL decoding error messages rahul
  • Re: Wrong LSN in WAL decoding error messages surya poondla
  • Re: Wrong LSN in WAL decoding error messages Rahul
  • Re: Wrong LSN in WAL decoding error messages surya poondla
• [PATCH] psql: avoid CREATE command completion after GRANT/REVOKE CREATE Haruna Miwa
  • Re: [PATCH] psql: avoid CREATE command completion after GRANT/REVOKE CREATE Sho Ito
  • Re: [PATCH] psql: avoid CREATE command completion after GRANT/REVOKE CREATE Haruna Miwa
  • Re: [PATCH] psql: avoid CREATE command completion after GRANT/REVOKE CREATE Sho Ito
  • Re: [PATCH] psql: avoid CREATE command completion after GRANT/REVOKE CREATE Fujii Masao
  • Re: [PATCH] psql: avoid CREATE command completion after GRANT/REVOKE CREATE Haruna Miwa
  • Re: [PATCH] psql: avoid CREATE command completion after GRANT/REVOKE CREATE Fujii Masao
• Re: Correct documentation for protocol version shihao zhong
  • Re: Correct documentation for protocol version solai v
• Material node can report incorrect "Maximum Storage" in EXPLAIN David Rowley
  • Re: Material node can report incorrect "Maximum Storage" in EXPLAIN Tatsuo Ishii
  • Re: Material node can report incorrect "Maximum Storage" in EXPLAIN Tatsuya Kawata
  • Re: Material node can report incorrect "Maximum Storage" in EXPLAIN David Rowley
• Commitfest PG20-2 is now closed shihao zhong
  • Re: Commitfest PG20-2 is now closed Álvaro Herrera
  • Re: Commitfest PG20-2 is now closed Jacob Champion
  • Re: Commitfest PG20-2 is now closed Jelte Fennema-Nio
  • Re: Commitfest PG20-2 is now closed shihao zhong
• Re: Report index currently being vacuumed in pg_stat_progress_vacuum Michael Paquier
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum Michael Paquier
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum Sami Imseih
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum Michael Paquier
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum Michael Paquier
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum shihao zhong
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum Bharath Rupireddy
• WITHOUT OVERLAPS foreign key allows referencing EXCLUDE constraint Paul A Jungwirth
• Re: Document that jsonpath == can be used as ANY Marcos Pegoraro
  • Re: Document that jsonpath == can be used as ANY David G. Johnston
  • Re: Document that jsonpath == can be used as ANY Marcos Pegoraro
  • Re: Document that jsonpath == can be used as ANY David G. Johnston
• Re: Recovery does not honor io_combine_limit, causing IOPS saturation Mats Kindahl
• Session in aborted transaction misses effective_wal_level change Sergei Patiakin
  • Re: Session in aborted transaction misses effective_wal_level change Masahiko Sawada
  • RE: Session in aborted transaction misses effective_wal_level change Hayato Kuroda (Fujitsu)
  • Re: Session in aborted transaction misses effective_wal_level change Sergei Patiakin
  • Re: Session in aborted transaction misses effective_wal_level change Masahiko Sawada
  • Re: Session in aborted transaction misses effective_wal_level change Bertrand Drouvot
  • RE: Session in aborted transaction misses effective_wal_level change Hayato Kuroda (Fujitsu)
  • Re: Session in aborted transaction misses effective_wal_level change Masahiko Sawada
  • RE: Session in aborted transaction misses effective_wal_level change Hayato Kuroda (Fujitsu)
  • Re: Session in aborted transaction misses effective_wal_level change Sergei Patiakin
  • Re: Session in aborted transaction misses effective_wal_level change Masahiko Sawada
  • Re: Session in aborted transaction misses effective_wal_level change Bertrand Drouvot
  • Re: Session in aborted transaction misses effective_wal_level change Shlok Kyal
• Re: Residual cleanups for tied objects in PL/Perl Kirill Reshke
  • Re: Residual cleanups for tied objects in PL/Perl Andrey Rachitskiy
• REPACK (CONCURRENTLY) might keep dropped-column data Radim Marek
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data Radim Marek
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data Álvaro Herrera
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data Antonin Houska
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data Radim Marek
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data Alvaro Herrera
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data Fujii Masao
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data Alvaro Herrera
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data shihao zhong
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data Antonin Houska
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data Antonin Houska
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data shihao zhong
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data Alvaro Herrera
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data shihao zhong
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data Fujii Masao
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data Fujii Masao
  • Re: REPACK (CONCURRENTLY) might keep dropped-column data Alvaro Herrera
• Re: Open SSI correctness issues Aleksander Alekseev
  • Re: Open SSI correctness issues Andrey Borodin
  • Re: Open SSI correctness issues Aleksander Alekseev
• WG: AW: Extract text from XML, pay attention to XML Entities StMUK
  • AW: AW: Extract text from XML, pay attention to XML Entities StMUK
  • Re: Extract text from XML, pay attention to XML Entities David G. Johnston
• Re: on_error table, saving error info to a table jian he
• Re: postgres_fdw: transaction mode inheritance corner cases Etsuro Fujita
  • Re: postgres_fdw: transaction mode inheritance corner cases Matheus Alcantara
  • Re: postgres_fdw: transaction mode inheritance corner cases Nikolay Samokhvalov
  • Re: postgres_fdw: transaction mode inheritance corner cases Etsuro Fujita
  • Re: postgres_fdw: transaction mode inheritance corner cases Etsuro Fujita
  • Re: postgres_fdw: transaction mode inheritance corner cases Matheus Alcantara
  • Re: postgres_fdw: transaction mode inheritance corner cases Etsuro Fujita
  • Re: postgres_fdw: transaction mode inheritance corner cases Etsuro Fujita
  • Re: postgres_fdw: transaction mode inheritance corner cases Matheus Alcantara
  • Re: postgres_fdw: transaction mode inheritance corner cases Etsuro Fujita
  • Re: postgres_fdw: transaction mode inheritance corner cases Nikolay Samokhvalov
  • Re: postgres_fdw: transaction mode inheritance corner cases Etsuro Fujita
  • Re: postgres_fdw: transaction mode inheritance corner cases Matheus Alcantara
  • Re: postgres_fdw: transaction mode inheritance corner cases Etsuro Fujita
  • Re: postgres_fdw: transaction mode inheritance corner cases Matheus Alcantara
  • Re: postgres_fdw: transaction mode inheritance corner cases Etsuro Fujita
  • Re: postgres_fdw: transaction mode inheritance corner cases Matheus Alcantara
  • Re: postgres_fdw: transaction mode inheritance corner cases Etsuro Fujita
  • Re: postgres_fdw: transaction mode inheritance corner cases Etsuro Fujita
• [PATCH v1] Fix out-of-bounds access in pg_bsd_indent's parser stack Vadim Shakirov
  • Re: [PATCH v1] Fix out-of-bounds access in pg_bsd_indent's parser stack Daniel Gustafsson
  • Re: [PATCH v1] Fix out-of-bounds access in pg_bsd_indent's parser stack Álvaro Herrera
  • Re: [PATCH v1] Fix out-of-bounds access in pg_bsd_indent's parser stack Daniel Gustafsson
• Re: Do we want to avoid checksumming extra files in the datadir? [was: BUG #19647] Rui Zhao
  • Re: Do we want to avoid checksumming extra files in the datadir? [was: BUG #19647] Shubhra Jain
• remote_apply commit hangs when wal_receiver_status_interval = 0 Vaibhav Dalvi
  • Re: remote_apply commit hangs when wal_receiver_status_interval = 0 Ashutosh Sharma
  • Re: remote_apply commit hangs when wal_receiver_status_interval = 0 Vaibhav Dalvi
  • Re: remote_apply commit hangs when wal_receiver_status_interval = 0 Fujii Masao
  • Re: remote_apply commit hangs when wal_receiver_status_interval = 0 Vaibhav Dalvi
  • Re: remote_apply commit hangs when wal_receiver_status_interval = 0 Fujii Masao
• Re: docs: Include database collation check on SQL from alter_collation.sgml Shubhra Jain
• Re: meson: pass OpenSSL/ICU include dirs to extensions Grigorev Jurij
  • Re: meson: pass OpenSSL/ICU include dirs to extensions Aidar Imamov
  • Re: meson: pass OpenSSL/ICU include dirs to extensions Aidar Imamov
  • Re: meson: pass OpenSSL/ICU include dirs to extensions Harrison Booth
• REPACK (CONCURRENTLY): do not block the table while waiting for the final lock shihao zhong
  • Re: REPACK (CONCURRENTLY): do not block the table while waiting for the final lock Antonin Houska
  • Re: REPACK (CONCURRENTLY): do not block the table while waiting for the final lock Alvaro Herrera
  • Re: REPACK (CONCURRENTLY): do not block the table while waiting for the final lock shihao zhong
• Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners Paul Kim
• Two fixes for parallel query cleanup: DSM detach order and a stray statement timeout shihao zhong
• Re: Assert failure in get_baserel_parampathinfo with lateral UNION ALL Richard Guo
  • Re: Assert failure in get_baserel_parampathinfo with lateral UNION ALL Richard Guo
• Do we need to back-patch tzcode 2026b after all? Tom Lane
  • Re: Do we need to back-patch tzcode 2026b after all? Daniel Gustafsson
  • Re: Do we need to back-patch tzcode 2026b after all? Tom Lane
• Re: Improve cube GiST page splits Rustam ALLAKOV
• Re: using index to speedup add not null constraints to a table jian he
• Re: pg_walinspect: add functions to locate and list WAL by time and LSN surya poondla
  • Re: pg_walinspect: add functions to locate and list WAL by time and LSN Chao Li
  • Re: pg_walinspect: add functions to locate and list WAL by time and LSN surya poondla
  • Re: pg_walinspect: add functions to locate and list WAL by time and LSN Chao Li
  • Re: pg_walinspect: add functions to locate and list WAL by time and LSN surya poondla
  • Re: pg_walinspect: add functions to locate and list WAL by time and LSN Chao Li
  • Re: pg_walinspect: add functions to locate and list WAL by time and LSN surya poondla
  • Re: pg_walinspect: add functions to locate and list WAL by time and LSN Chao Li
  • Re: pg_walinspect: add functions to locate and list WAL by time and LSN surya poondla
• [PATCH] intXshr, intXshl: return error on shift count out of range Egor Ivkov
  • Re: [PATCH] intXshr, intXshl: return error on shift count out of range Egor Ivkov
  • Re: [PATCH] intXshr, intXshl: return error on shift count out of range Egor Ivkov
  • Re: [PATCH] intXshr, intXshl: return error on shift count out of range Pavel Borisov
  • Re: [PATCH] intXshr, intXshl: return error on shift count out of range Alexander Lakhin

• Earlier messages
• Later messages