pgsql-hackers  

Messages by Thread

• • Re: hashjoins vs. Bloom filters (yet again) Andrei Lepikhov
  • Re: hashjoins vs. Bloom filters (yet again) Tomas Vondra
• Re: Unexpected reindex when altering column types for partitioned tables Álvaro Rodríguez
• Re: Vacuum statistics Alena Rybakina
• 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 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 Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication Zhijie Hou
  • Re: Proposal: Conflict log history table for Logical Replication Masahiko Sawada
  • 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 Narayanan Venkateswaran
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Zhijie Hou
  • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • 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 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: create table like including storage parameter Fujii Masao
  • Re: create table like including storage parameter jian he
• Re: Typo in version check in postgresAcquireSampleRowsFunc Etsuro Fujita
• Re: Publication DDL can race with a concurrent UPDATE shveta malik
  • Re: Publication DDL can race with a concurrent UPDATE shveta malik
  • Re: Publication DDL can race with a concurrent UPDATE Zhijie Hou
  • Re: Publication DDL can race with a concurrent UPDATE vignesh C
  • Re: Publication DDL can race with a concurrent UPDATE Nikhil Sontakke
  • Re: Publication DDL can race with a concurrent UPDATE vignesh C
  • Re: Publication DDL can race with a concurrent UPDATE Nikhil Sontakke
• 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: ON CONFLICT DO SELECT returns rows hidden by a view jian he
• 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
• LWLock granular partition lock memory layout Alexandre Felipe
  • Re: LWLock granular partition lock memory layout Alexandre Felipe
  • Re: LWLock granular partition lock memory layout Nathan Bossart
  • Re: LWLock granular partition lock memory layout Alexandre Felipe
  • Re: LWLock granular partition lock memory layout Alexandre Felipe
• 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: ERROR: too late to create a new PlaceHolderInfo Richard Guo
  • Re: ERROR: too late to create a new PlaceHolderInfo Richard Guo
  • Re: ERROR: too late to create a new PlaceHolderInfo Richard Guo
• Re: Why clearing the VM doesn't require registering vm buffer in wal record Andrey Borodin
  • Re: Why clearing the VM doesn't require registering vm buffer in wal record Melanie Plageman
  • Re: Why clearing the VM doesn't require registering vm buffer in wal record Amit Kapila
• Re: Proposal: Supporting URI SAN in Certificate Authentication Florin Irion
  • Re: Proposal: Supporting URI SAN in Certificate Authentication Agustín Martínez Fayó
• Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Matheus Alcantara
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Matheus Alcantara
  • Re: PG19: two RI fast-path issues found while testing the batching revert Melanie Plageman
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Fujii Masao
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
• Two more RI fast-path issues Amit Langote
  • Re: Two more RI fast-path issues Amit Langote
  • Re: Two more RI fast-path issues Amit Langote
  • Re: Two more RI fast-path issues Amit Langote
  • Re: Two more RI fast-path issues Tom Lane
  • Re: Two more RI fast-path issues Amit Langote
  • Re: Two more RI fast-path issues Amit Langote
  • Re: Two more RI fast-path issues Lucas Jeffrey
  • Re: Two more RI fast-path issues Amit Langote
  • Re: Two more RI fast-path issues Amit Langote
• Re: Warn when creating or enabling a subscription with max_logical_replication_workers = 0 Shubhra Jain
• Re: subquery pullup misses lateral refs in join alias Vars Richard Guo
• should pg_dumpall --clean apply to database in --exclude-database jian he
  • Re: should pg_dumpall --clean apply to database in --exclude-database David G. Johnston
• Re: [PATCH] Extend MXactCache lifetime from per-transaction to per-session JoongHyuk Shin
• 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: gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower Vaibhav Dalvi
  • Re: gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower Vaibhav Dalvi
  • Re: gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower Vaibhav Dalvi
• Re: Fix reindexdb with parallel index-level conrurrent run Michael Paquier
  • Re: Fix reindexdb with parallel index-level conrurrent run Kirill Reshke
  • Re: Fix reindexdb with parallel index-level conrurrent run Michael Paquier
  • Re: Fix reindexdb with parallel index-level conrurrent run Michael Paquier
  • Re: Fix reindexdb with parallel index-level conrurrent run Manu
• Re: Compression of bigger WAL records Michael Paquier
  • Re: Compression of bigger WAL records Andrey Borodin
  • Re: Compression of bigger WAL records Michael Paquier
  • Re: Compression of bigger WAL records Andrey Borodin
  • Re: Compression of bigger WAL records Michael Paquier
  • Re: Compression of bigger WAL records Michael Paquier
  • Re: Compression of bigger WAL records Andrey Borodin
  • Re: Compression of bigger WAL records Michael Paquier
  • Re: Compression of bigger WAL records Zsolt Parragi
  • Re: Compression of bigger WAL records Zsolt Parragi
• [PG19] Wrong results from NOT NULL-based expression simplification shihao zhong
  • Re: [PG19] Wrong results from NOT NULL-based expression simplification Melanie Plageman
  • Re: [PG19] Wrong results from NOT NULL-based expression simplification shihao zhong
  • Re: [PG19] Wrong results from NOT NULL-based expression simplification Richard Guo
  • Re: [PG19] Wrong results from NOT NULL-based expression simplification Haibo Yan
  • Re: [PG19] Wrong results from NOT NULL-based expression simplification Fujii Masao
  • Re: [PG19] Wrong results from NOT NULL-based expression simplification Richard Guo

• Earlier messages
• Later messages