pgsql-hackers  

Messages by Thread

• • 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: [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
  • Re: [PATCH] intXshr, intXshl: return error on shift count out of range Tom Lane
  • 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 David Rowley
  • Re: [PATCH] intXshr, intXshl: return error on shift count out of range Tom Lane
  • Re: [PATCH] intXshr, intXshl: return error on shift count out of range David Rowley
  • 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 Tom Lane
  • Re: [PATCH] intXshr, intXshl: return error on shift count out of range David Rowley
  • 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 David Rowley
  • Re: [PATCH] intXshr, intXshl: return error on shift count out of range Tom Lane
• Re: Proposal: Conflict log history table for Logical Replication kedar anavardekar
  • 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
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • 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 shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shihao zhong
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shihao zhong
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shihao zhong
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Zhijie Hou
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication Masahiko Sawada
  • 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 shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Zhijie Hou
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Zhijie Hou
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Zhijie Hou
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • 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 Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Zsolt Parragi
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Zsolt Parragi
  • 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 Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
• Re: BUG #19686: Rolling back SET TABLESPACE Tom Lane
  • Re: BUG #19686: Rolling back SET TABLESPACE Alexandre Felipe
  • Re: BUG #19686: Rolling back SET TABLESPACE Alexandre Felipe
  • Re: BUG #19686: Rolling back SET TABLESPACE Manu
  • Re: BUG #19686: Rolling back SET TABLESPACE shihao zhong
  • Re: BUG #19686: Rolling back SET TABLESPACE Alexandre Felipe
  • Re: BUG #19686: Rolling back SET TABLESPACE Manu
  • Re: BUG #19686: Rolling back SET TABLESPACE Alexandre Felipe
  • Re: BUG #19686: Rolling back SET TABLESPACE Manu
  • Re: BUG #19686: Rolling back SET TABLESPACE Andres Freund
  • Re: BUG #19686: Rolling back SET TABLESPACE Manu
  • Re: BUG #19686: Rolling back SET TABLESPACE shihao zhong
  • Re: BUG #19686: Rolling back SET TABLESPACE Manu
  • Re: BUG #19686: Rolling back SET TABLESPACE shihao zhong
  • Re: BUG #19686: Rolling back SET TABLESPACE shihao zhong
  • Re: BUG #19686: Rolling back SET TABLESPACE Manu
  • Re: BUG #19686: Rolling back SET TABLESPACE shihao zhong
  • Re: BUG #19686: Rolling back SET TABLESPACE Manu
  • Re: BUG #19686: Rolling back SET TABLESPACE Andres Freund
  • Re: BUG #19686: Rolling back SET TABLESPACE Tom Lane
• 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: 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: 64-bit MultiXactOffset vs. 9.3->9.4 upgrade, pg_resetwal, "wraparound" msg Heikki Linnakangas
• Re: [PATCH] Two remaining shmem attachment issues in single-user mode Heikki Linnakangas
  • Re: [PATCH] Two remaining shmem attachment issues in single-user mode Ashutosh Bapat
  • Re: [PATCH] Two remaining shmem attachment issues in single-user mode Alexander Lakhin
  • Re: [PATCH] Two remaining shmem attachment issues in single-user mode Ayush Tiwari
  • Re: [PATCH] Two remaining shmem attachment issues in single-user mode Heikki Linnakangas
• 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: Typo in version check in postgresAcquireSampleRowsFunc Etsuro Fujita
  • Re: Typo in version check in postgresAcquireSampleRowsFunc Etsuro Fujita
  • Re: Typo in version check in postgresAcquireSampleRowsFunc Etsuro Fujita
• Re: Support for 8-byte TOAST values, round two Hannu Krosing
  • Re: Support for 8-byte TOAST values, round two Michael Paquier
• Re: Fix apply worker crash when subscriber table has only a deferrable primary key Nisha Moond
  • RE: Fix apply worker crash when subscriber table has only a deferrable primary key Hayato Kuroda (Fujitsu)
  • Re: Fix apply worker crash when subscriber table has only a deferrable primary key vignesh C
  • Re: Fix apply worker crash when subscriber table has only a deferrable primary key Zhijie Hou
  • Re: Fix apply worker crash when subscriber table has only a deferrable primary key Nisha Moond
  • Re: Fix apply worker crash when subscriber table has only a deferrable primary key vignesh C
  • Re: Fix apply worker crash when subscriber table has only a deferrable primary key Zhijie Hou
  • Re: Fix apply worker crash when subscriber table has only a deferrable primary key Nisha Moond
  • Re: Fix apply worker crash when subscriber table has only a deferrable primary key Amit Kapila
  • Re: Fix apply worker crash when subscriber table has only a deferrable primary key Zhijie Hou
  • Re: Fix apply worker crash when subscriber table has only a deferrable primary key Amit Kapila
  • Re: Fix apply worker crash when subscriber table has only a deferrable primary key Nisha Moond
  • RE: Fix apply worker crash when subscriber table has only a deferrable primary key Hayato Kuroda (Fujitsu)
  • Re: Fix apply worker crash when subscriber table has only a deferrable primary key Zhijie Hou
  • Re: Fix apply worker crash when subscriber table has only a deferrable primary key Nisha Moond
  • RE: Fix apply worker crash when subscriber table has only a deferrable primary key Hayato Kuroda (Fujitsu)
• Re: Persist slot invalidations before publishing them Ashutosh Sharma
  • Re: Persist slot invalidations before publishing them Bertrand Drouvot
  • Re: Persist slot invalidations before publishing them Ashutosh Sharma
  • Re: Persist slot invalidations before publishing them Bertrand Drouvot
  • Re: Persist slot invalidations before publishing them shveta malik
  • Re: Persist slot invalidations before publishing them Bertrand Drouvot
  • Re: Persist slot invalidations before publishing them shveta malik
  • Re: Persist slot invalidations before publishing them Bertrand Drouvot
  • Re: Persist slot invalidations before publishing them Bertrand Drouvot
  • Re: Persist slot invalidations before publishing them Ashutosh Sharma
  • Re: Persist slot invalidations before publishing them Bertrand Drouvot
  • Re: Persist slot invalidations before publishing them Bertrand Drouvot
• Re: Temporary slot leak when creation fails in a subtransaction shveta malik
• Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ Rahul Yadav
  • Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ Michael Paquier
  • Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ Grigorev Jurij

• Later messages