pgsql-hackers  

Messages by Thread

• • Re: GiST multirange index scans can fail to return rows Alexander Korotkov
  • Re: GiST multirange index scans can fail to return rows Andrey Borodin
• ANSI SQL proposal: SELECT DISTINCT ON (... ORDER BY ...) and UNION DISTINCT ON (... ORDER BY ...) Hannu Krosing
• Re: a large LIMIT makes some sorts slower Chengpeng Yan
  • Re: a large LIMIT makes some sorts slower Tatsuya Kawata
  • Re: a large LIMIT makes some sorts slower Chengpeng Yan
• Reduce memory overheads for storing a Memoize tuple David Rowley
  • Re: Reduce memory overheads for storing a Memoize tuple Chao Li
  • Re: Reduce memory overheads for storing a Memoize tuple David Rowley
  • Re: Reduce memory overheads for storing a Memoize tuple Chao Li
  • Re: Reduce memory overheads for storing a Memoize tuple David Rowley
  • Re: Reduce memory overheads for storing a Memoize tuple Michael Paquier
  • Re: Reduce memory overheads for storing a Memoize tuple Andrey Borodin
  • Re: Reduce memory overheads for storing a Memoize tuple David Rowley
  • Re: Reduce memory overheads for storing a Memoize tuple Michael Paquier
• ALTER COLUMN SET EXPRESSION on partitions not work in case of constraint dependencies jian he
  • Re: ALTER COLUMN SET EXPRESSION on partitions not work in case of constraint dependencies jian he
  • Re: ALTER COLUMN SET EXPRESSION on partitions not work in case of constraint dependencies Alberto Piai
  • Re: ALTER COLUMN SET EXPRESSION on partitions not work in case of constraint dependencies jian he
  • Re: ALTER COLUMN SET EXPRESSION on partitions not work in case of constraint dependencies Alberto Piai
  • Re: ALTER COLUMN SET EXPRESSION on partitions not work in case of constraint dependencies jian he
• RI fast path gets cross-type foreign keys wrong Peter Geoghegan
  • Re: RI fast path gets cross-type foreign keys wrong Amit Langote
  • Re: RI fast path gets cross-type foreign keys wrong Amit Langote
  • Re: RI fast path gets cross-type foreign keys wrong Mihail Nikalayeu
  • Re: RI fast path gets cross-type foreign keys wrong Amit Langote
  • Re: RI fast path gets cross-type foreign keys wrong Mihail Nikalayeu
  • Re: RI fast path gets cross-type foreign keys wrong Amit Langote
  • Re: RI fast path gets cross-type foreign keys wrong Amit Langote
  • Re: RI fast path gets cross-type foreign keys wrong Amit Langote
  • Re: RI fast path gets cross-type foreign keys wrong Amit Langote
  • Re: RI fast path gets cross-type foreign keys wrong Peter Geoghegan
  • Re: RI fast path gets cross-type foreign keys wrong Amit Langote
• Re: [Patch]The Case For WAL-Logging pg_upgrade John Naylor
  • Re: [Patch]The Case For WAL-Logging pg_upgrade Bohyun Lee
  • Re: [Patch]The Case For WAL-Logging pg_upgrade John Naylor
  • Re: [Patch]The Case For WAL-Logging pg_upgrade Bohyun Lee
  • Re: [Patch]The Case For WAL-Logging pg_upgrade John Naylor
  • Re: [Patch]The Case For WAL-Logging pg_upgrade Heikki Linnakangas
  • Re: [Patch]The Case For WAL-Logging pg_upgrade John Naylor
  • Re: [Patch]The Case For WAL-Logging pg_upgrade Heikki Linnakangas
  • Re: [Patch]The Case For WAL-Logging pg_upgrade John Naylor
  • Re: [Patch]The Case For WAL-Logging pg_upgrade Hüseyin Demir
  • Re: [Patch]The Case For WAL-Logging pg_upgrade Marco Nenciarini
• Re: pg19b1: TRAP: failed Assert("pgstat_bktype_io_stats_valid(bktype_shstats, MyBackendType)") Melanie Plageman
  • Re: pg19b1: TRAP: failed Assert("pgstat_bktype_io_stats_valid(bktype_shstats, MyBackendType)") Melanie Plageman
• Re: Asynchronous MergeAppend Alexander Korotkov
  • Re: Asynchronous MergeAppend Alexander Pyhalov
  • Re: Asynchronous MergeAppend Alexander Pyhalov
  • Re: Asynchronous MergeAppend Etsuro Fujita
  • Re: Asynchronous MergeAppend Alexander Pyhalov
  • Re: Asynchronous MergeAppend Etsuro Fujita
  • Re: Asynchronous MergeAppend Etsuro Fujita
• Re: add list of major features to the v19 release notes Nathan Bossart
  • Re: add list of major features to the v19 release notes Jonathan S. Katz
  • Re: add list of major features to the v19 release notes Andrew Dunstan
  • Re: add list of major features to the v19 release notes Nathan Bossart
  • Re: add list of major features to the v19 release notes Jonathan S. Katz
• Re: walsummarizer can get stuck when switching timelines Robert Haas
  • Re: walsummarizer can get stuck when switching timelines Alexander Lakhin
  • Re: walsummarizer can get stuck when switching timelines Andrey Borodin
  • Re: walsummarizer can get stuck when switching timelines Robert Haas
  • Re: walsummarizer can get stuck when switching timelines Alexander Lakhin
  • Re: walsummarizer can get stuck when switching timelines Andrey Borodin
  • Re: walsummarizer can get stuck when switching timelines Alexander Lakhin
  • Re: walsummarizer can get stuck when switching timelines Andrey Borodin
• Re: Fold NOT IN / <> ALL expressions containing NULL to FALSE Yugo Nagata
  • Re: Fold NOT IN / <> ALL expressions containing NULL to FALSE Ilia Evdokimov
• Re: glibc qsort() vulnerability Nathan Bossart
• Re: Prove a NOT IN's left-hand expressions non-nullable from quals Rui Zhao
  • Re: Prove a NOT IN's left-hand expressions non-nullable from quals Richard Guo
  • Re: Prove a NOT IN's left-hand expressions non-nullable from quals wenhui qiu
  • Re: Prove a NOT IN's left-hand expressions non-nullable from quals Rui Zhao
• Re: bump minimum supported version of psql and pg_{dump,dumpall,upgrade} to v10 Nathan Bossart
• Re: Implicit conversion from int64 to int32 when calling hash_get_num_entries Karina Litskevich
  • Re: Implicit conversion from int64 to int32 when calling hash_get_num_entries Daniel Gustafsson
  • Re: Implicit conversion from int64 to int32 when calling hash_get_num_entries Tom Lane
  • Re: Implicit conversion from int64 to int32 when calling hash_get_num_entries Karina Litskevich
  • Re: Implicit conversion from int64 to int32 when calling hash_get_num_entries Daniel Gustafsson
  • Re: Implicit conversion from int64 to int32 when calling hash_get_num_entries Karina Litskevich
• Re: hashjoins vs. Bloom filters (yet again) Tomas Vondra
  • Re: hashjoins vs. Bloom filters (yet again) Matheus Alcantara
  • Re: hashjoins vs. Bloom filters (yet again) Tomas Vondra
  • Re: hashjoins vs. Bloom filters (yet again) Matheus Alcantara
  • Re: hashjoins vs. Bloom filters (yet again) Matheus Alcantara
  • Re: hashjoins vs. Bloom filters (yet again) Matheus Alcantara
  • Re: hashjoins vs. Bloom filters (yet again) Matheus Alcantara
  • Re: hashjoins vs. Bloom filters (yet again) Tomas Vondra
  • Re: hashjoins vs. Bloom filters (yet again) Denis Rodionov
  • Re: hashjoins vs. Bloom filters (yet again) Tomas Vondra
  • Re: hashjoins vs. Bloom filters (yet again) Matheus Alcantara
  • Re: hashjoins vs. Bloom filters (yet again) Tomas Vondra
  • Re: hashjoins vs. Bloom filters (yet again) Tomas Vondra
  • Re: hashjoins vs. Bloom filters (yet again) Rui Zhao
  • Re: hashjoins vs. Bloom filters (yet again) Matheus Alcantara
  • Re: hashjoins vs. Bloom filters (yet again) Bruce Momjian
  • Re: hashjoins vs. Bloom filters (yet again) Tomas Vondra
  • Re: hashjoins vs. Bloom filters (yet again) Bruce Momjian
  • Re: hashjoins vs. Bloom filters (yet again) Tomas Vondra
  • Re: hashjoins vs. Bloom filters (yet again) Bruce Momjian
• Re: WAL compression setting after PostgreSQL LZ4 default change Christoph Berg
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Christoph Berg
  • Re: WAL compression setting after PostgreSQL LZ4 default change Andrey Borodin
  • Re: WAL compression setting after PostgreSQL LZ4 default change Christoph Berg
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Christoph Berg
  • Re: WAL compression setting after PostgreSQL LZ4 default change Japin Li
  • Re: WAL compression setting after PostgreSQL LZ4 default change Michael Paquier
  • Re: WAL compression setting after PostgreSQL LZ4 default change Andreas Karlsson
  • Re: WAL compression setting after PostgreSQL LZ4 default change Hannu Krosing
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Hannu Krosing
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Hannu Krosing
  • Re: WAL compression setting after PostgreSQL LZ4 default change Hannu Krosing
  • Re: WAL compression setting after PostgreSQL LZ4 default change Ken Marshall
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change wenhui qiu
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Andrey Borodin
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Christoph Berg
  • Re: WAL compression setting after PostgreSQL LZ4 default change Daniel Gustafsson
  • Re: WAL compression setting after PostgreSQL LZ4 default change Jelte Fennema-Nio
  • Re: WAL compression setting after PostgreSQL LZ4 default change Michael Paquier
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Christoph Berg
  • Re: WAL compression setting after PostgreSQL LZ4 default change Daniel Gustafsson
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change wenhui qiu
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
• Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Alberto Piai
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Alberto Piai
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Chao Li
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Melanie Plageman
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Sami Imseih
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Sami Imseih
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Chao Li
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Sami Imseih
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Chao Li
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Chao Li
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Zsolt Parragi
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Chao Li
  • RE: tablecmds: fix bug where index rebuild loses replica identity on partitions Zhijie Hou (Fujitsu)
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Chao Li
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Chao Li
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Sami Imseih
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Chao Li
• Re: Streaming replication and WAL archive interactions Andrey Borodin
• Re: Add a pg_wal_preallocate() SQL function to eagerly create future WAL segments solai v
  • 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 Nazir Bilal Yavuz
  • 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 Bharath Rupireddy
  • Re: Add a pg_wal_preallocate() SQL function to eagerly create future WAL segments Xuneng Zhou
  • 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 Bharath Rupireddy
  • 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 Bharath Rupireddy
  • 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 Bharath Rupireddy
  • 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 Nazir Bilal Yavuz
  • 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 Nazir Bilal Yavuz
• Add PQTRACE env to enable protocol tracing in libpq Anthonin Bonnefoy
  • Re: Add PQTRACE env to enable protocol tracing in libpq Jelte Fennema-Nio
• [PATCH] Fix timeline history after recovery stops on an ancestor Филиппов Степан
  • Re: [PATCH] Fix timeline history after recovery stops on an ancestor Andrey Rachitskiy
  • Re: [PATCH] Fix timeline history after recovery stops on an ancestor Andrey Borodin
• Re: DOCS QUESTION - space added within synopsis replaceable tag. Bruce Momjian
• Re: Per-table resync for logical replication subscriptions Cagri Biroglu
  • Re: Per-table resync for logical replication subscriptions Masahiko Sawada
  • Re: Per-table resync for logical replication subscriptions Cagri Biroglu
  • Re: Per-table resync for logical replication subscriptions Masahiko Sawada
  • Re: Per-table resync for logical replication subscriptions Cagri Biroglu
  • RE: Per-table resync for logical replication subscriptions Hayato Kuroda (Fujitsu)
  • Re: Per-table resync for logical replication subscriptions Cagri Biroglu
  • Re: Per-table resync for logical replication subscriptions Ajin Cherian
  • Re: Per-table resync for logical replication subscriptions Cagri Biroglu
  • RE: Per-table resync for logical replication subscriptions Hayato Kuroda (Fujitsu)
  • Re: Per-table resync for logical replication subscriptions Cagri Biroglu
  • Re: Per-table resync for logical replication subscriptions Yilin Zhang
  • Re: Per-table resync for logical replication subscriptions Cagri Biroglu
  • RE: Per-table resync for logical replication subscriptions Hayato Kuroda (Fujitsu)
  • Re: Per-table resync for logical replication subscriptions Cagri Biroglu
• Wrong results: NOT IN to anti-join with an upper-level Var in the sub-select's output Rui Zhao
  • Re: Wrong results: NOT IN to anti-join with an upper-level Var in the sub-select's output Tender Wang
  • Re: Wrong results: NOT IN to anti-join with an upper-level Var in the sub-select's output Rui Zhao
  • Re: Wrong results: NOT IN to anti-join with an upper-level Var in the sub-select's output Richard Guo
• Re: timestamp vs. timestamptz comparisons inconsistently ordered under DST Laurenz Albe
• Re: [Patch] Omit virtual generated columns from test_decoding output Bharath Rupireddy
  • Re: [Patch] Omit virtual generated columns from test_decoding output Masahiko Sawada
  • Re: [Patch] Omit virtual generated columns from test_decoding output Bharath Rupireddy
  • Re: [Patch] Omit virtual generated columns from test_decoding output Euler Taveira
  • Re: [Patch] Omit virtual generated columns from test_decoding output Bharath Rupireddy

• Earlier messages
• Later messages