pgsql-hackers  

Messages by Thread

• • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition Henson Choi
• Re: Extended statistics improvement: multi-column MCV missing values Enrique Sánchez
• Re: Offline data checksum changes can cause incorrect checksum state on standbys Alexander Lakhin
  • Re: Offline data checksum changes can cause incorrect checksum state on standbys Nazir Bilal Yavuz
• Re: Proposal: Supporting URI SAN in Certificate Authentication Agustín Martínez Fayó
  • Re: Proposal: Supporting URI SAN in Certificate Authentication Florin Irion
  • Re: Proposal: Supporting URI SAN in Certificate Authentication Agustín Martínez Fayó
  • Re: Proposal: Supporting URI SAN in Certificate Authentication Nico Williams
• Re: GIN index fast list search may become un-interruptible for long time. shihao zhong
• Hardening visibility-map maintenance and recovery Melanie Plageman
• Re: small cleanup for s_lock.h Nathan Bossart
  • Re: small cleanup for s_lock.h Nathan Bossart
• REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Radim Marek
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes shihao zhong
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Radim Marek
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Antonin Houska
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes shihao zhong
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Álvaro Herrera
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Antonin Houska
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Alvaro Herrera
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Alvaro Herrera
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Alvaro Herrera
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Antonin Houska
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Alvaro Herrera
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Radim Marek
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Antonin Houska
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Alvaro Herrera
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Alvaro Herrera
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Alvaro Herrera
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Nathan Bossart
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Alvaro Herrera
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes shihao zhong
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Radim Marek
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Alvaro Herrera
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Nathan Bossart
  • Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes Antonin Houska
• [PATCH] Table sync race with REFRESH PUBLICATION Ayush Tiwari
  • Re: [PATCH] Table sync race with REFRESH PUBLICATION Peter Smith
  • Re: [PATCH] Table sync race with REFRESH PUBLICATION Ayush Tiwari
  • Re: [PATCH] Table sync race with REFRESH PUBLICATION Peter Smith
  • Re: [PATCH] Table sync race with REFRESH PUBLICATION Ayush Tiwari
  • Re: [PATCH] Table sync race with REFRESH PUBLICATION Ayush Tiwari
• Re: [PATCH] btree_gist: add cross-type integer operator support for GiST Tom Lane
• Cleaning up pgcrypto/crypt-des.c to avoid compiler warnings Tom Lane
  • Re: Cleaning up pgcrypto/crypt-des.c to avoid compiler warnings Ayush Tiwari
  • Re: Cleaning up pgcrypto/crypt-des.c to avoid compiler warnings Tom Lane
  • Re: Cleaning up pgcrypto/crypt-des.c to avoid compiler warnings Nathan Bossart
  • Re: Cleaning up pgcrypto/crypt-des.c to avoid compiler warnings Tom Lane
• Temporary slot leak when creation fails in a subtransaction Bharath Rupireddy
  • RE: Temporary slot leak when creation fails in a subtransaction Hayato Kuroda (Fujitsu)
  • Re: Temporary slot leak when creation fails in a subtransaction shveta malik
  • Re: Temporary slot leak when creation fails in a subtransaction shveta malik
  • Re: Temporary slot leak when creation fails in a subtransaction Narayanan Venkateswaran
  • Re: Temporary slot leak when creation fails in a subtransaction Bharath Rupireddy
  • Re: Temporary slot leak when creation fails in a subtransaction shveta malik
• Re: WAIT FOR command should do some query jumbling Sami Imseih
• REPACK (CONCURRENTLY) can lose data in pg_dump output Thom Brown
  • Re: REPACK (CONCURRENTLY) can lose data in pg_dump output Sami Imseih
  • Re: REPACK (CONCURRENTLY) can lose data in pg_dump output shihao zhong
  • Re: REPACK (CONCURRENTLY) can lose data in pg_dump output Thom Brown
• Re: Optimize MCV stats for sortable types and utilize sorted-order properties ZizhuanLiu X-MAN
  • Re: Optimize MCV stats for sortable types and utilize sorted-order properties ZizhuanLiu X-MAN
  • Re: Optimize MCV stats for sortable types and utilize sorted-order properties ZizhuanLiu X-MAN
  • Re: Optimize MCV stats for sortable types and utilize sorted-order properties ZizhuanLiu X-MAN
  • Re: Optimize MCV stats for sortable types and utilize sorted-order properties ZizhuanLiu X-MAN
  • Re: Optimize MCV stats for sortable types and utilize sorted-order properties ZizhuanLiu X-MAN
• Re: amcheck: support for GiST shihao zhong
• parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Sami Imseih
  • Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Bharath Rupireddy
  • Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Sami Imseih
  • Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Zsolt Parragi
  • Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Masahiko Sawada
  • Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Sami Imseih
  • Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Bharath Rupireddy
  • Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Sami Imseih
  • Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Bharath Rupireddy
  • Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Sami Imseih
  • Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Bharath Rupireddy
  • Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Michael Paquier
  • Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Masahiko Sawada
  • Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Masahiko Sawada
  • Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers Masahiko Sawada
• Re: Add a pg_wal_preallocate() SQL function to eagerly create future WAL segments Ayush Tiwari
  • Re: Add a pg_wal_preallocate() SQL function to eagerly create future WAL segments Ayush Tiwari
  • Re: Add a pg_wal_preallocate() SQL function to eagerly create future WAL segments Ayush Tiwari
• Redesign the EXPLAIN metric ‘Removed by Join Filter’? Andrei Lepikhov
• Re: REPACK: warn about skipping foreign partitions shihao zhong
  • Re: REPACK: warn about skipping foreign partitions Zsolt Parragi
  • Re: REPACK: warn about skipping foreign partitions shihao zhong
  • Re: REPACK: warn about skipping foreign partitions Zsolt Parragi
  • Re: REPACK: warn about skipping foreign partitions Fujii Masao
  • Re: REPACK: warn about skipping foreign partitions Zsolt Parragi
  • Re: REPACK: warn about skipping foreign partitions Fujii Masao
  • Re: REPACK: warn about skipping foreign partitions Zsolt Parragi
  • Re: REPACK: warn about skipping foreign partitions solai v
  • Re: REPACK: warn about skipping foreign partitions surya poondla
  • Re: REPACK: warn about skipping foreign partitions Zsolt Parragi
  • Re: REPACK: warn about skipping foreign partitions Fujii Masao
  • Re: REPACK: warn about skipping foreign partitions surya poondla
  • Re: REPACK: warn about skipping foreign partitions Fujii Masao
• Re: [PATCH] add missed tests for gist index shihao zhong
  • Re: [PATCH] add missed tests for gist index shihao zhong
  • Re: [PATCH] add missed tests for gist index Sho Ito
• Re: remove_useless_joins vs. bug #19560 Ayush Tiwari
  • Re: remove_useless_joins vs. bug #19560 Ayush Tiwari
  • Re: remove_useless_joins vs. bug #19560 Richard Guo
  • Re: remove_useless_joins vs. bug #19560 Richard Guo
  • Re: remove_useless_joins vs. bug #19560 Noah Misch
  • Re: remove_useless_joins vs. bug #19560 Tom Lane
  • Re: remove_useless_joins vs. bug #19560 Tom Lane
  • Re: remove_useless_joins vs. bug #19560 Tom Lane
  • Re: remove_useless_joins vs. bug #19560 Ayush Tiwari
  • Re: remove_useless_joins vs. bug #19560 Tom Lane
• Server crash when describing a FETCH statement after its cursor is closed Dirkjan Bussink
  • Re: Server crash when describing a FETCH statement after its cursor is closed Tom Lane
  • Re: Server crash when describing a FETCH statement after its cursor is closed Dirkjan Bussink
  • Re: Server crash when describing a FETCH statement after its cursor is closed Dirkjan Bussink
  • Re: Server crash when describing a FETCH statement after its cursor is closed Michael Paquier
  • Re: Server crash when describing a FETCH statement after its cursor is closed Michael Paquier
• Re: Remove invalid SS2/SS3 handling from EUC-KR routines John Naylor
  • Re: Remove invalid SS2/SS3 handling from EUC-KR routines SungJun Jang
• [PATCH] Fix TAP tests with recent IPC::Run on Windows Andrew Bille
  • Re: [PATCH] Fix TAP tests with recent IPC::Run on Windows Nazir Bilal Yavuz
  • Re: [PATCH] Fix TAP tests with recent IPC::Run on Windows Andrew Bille
  • Re: [PATCH] Fix TAP tests with recent IPC::Run on Windows Michael Paquier
  • Re: [PATCH] Fix TAP tests with recent IPC::Run on Windows Andrew Dunstan
  • Re: [PATCH] Fix TAP tests with recent IPC::Run on Windows Michael Paquier
  • Re: [PATCH] Fix TAP tests with recent IPC::Run on Windows Nazir Bilal Yavuz
  • Re: [PATCH] Fix TAP tests with recent IPC::Run on Windows Andrew Dunstan
• Re: WAL segment file descriptor leak on read errors can PANIC the server Michael Paquier
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bharath Rupireddy
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bharath Rupireddy
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Michael Paquier
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bharath Rupireddy
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Michael Paquier
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bertrand Drouvot
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Alexandre Felipe
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Michael Paquier
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Michael Paquier
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bertrand Drouvot
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bharath Rupireddy
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Michael Paquier
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bertrand Drouvot
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bharath Rupireddy
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bertrand Drouvot
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Michael Paquier
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Chao Li
• Re: RFC: Allow EXPLAIN to Output Page Fault Information torikoshia
• Re: Declare variable-length catalog columns as [] rather than [1] Peter Eisentraut
• Re: RFC: Logging plan of the running query torikoshia
  • Re: RFC: Logging plan of the running query torikoshia
• WAIT for LSN does not reject small negative timeouts Kirill Reshke
  • Re: WAIT for LSN does not reject small negative timeouts Daniel Gustafsson
  • Re: WAIT for LSN does not reject small negative timeouts Masahiko Sawada
• RE: Allow pg_read_all_stats to read replication origin status Hayato Kuroda (Fujitsu)
  • Re: Allow pg_read_all_stats to read replication origin status Virender Singla
  • Re: Allow pg_read_all_stats to read replication origin status Shubhra Jain
• Re: Proposal: Conflict log history table for Logical Replication kedar anavardekar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Narayanan Venkateswaran
  • Re: Proposal: Conflict log history table for Logical Replication Narayanan Venkateswaran
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication Narayanan Venkateswaran
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication Narayanan Venkateswaran
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication vignesh C
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication vignesh C
  • Re: Proposal: Conflict log history table for Logical Replication Narayanan Venkateswaran
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Narayanan Venkateswaran
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik

• Earlier messages
• Later messages