pgsql-hackers  

Messages by Thread

• • 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 Manu
  • Re: [PG19] Wrong results from NOT NULL-based expression simplification shihao zhong
  • Re: [PG19] Wrong results from NOT NULL-based expression simplification Dean Rasheed
  • Re: [PG19] Wrong results from NOT NULL-based expression simplification 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 jian he
  • Re: Row pattern recognition jian he
  • 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: [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock) Paul A Jungwirth
  • Re: [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock) solai v
• RE: Fix apply worker crash when subscriber table has only a deferrable primary key Hayato Kuroda (Fujitsu)
• 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 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
• [PG19] eager aggregation gives wrong results because of bpchar_ops shihao zhong
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Tom Lane
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops shihao zhong
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Tom Lane
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Peter Geoghegan
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Peter Geoghegan
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Tom Lane
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Peter Geoghegan
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Tom Lane
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Tom Lane
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Peter Geoghegan
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Tom Lane
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Tom Lane
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Peter Geoghegan
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Tom Lane
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Peter Geoghegan
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Tom Lane
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Peter Geoghegan
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops shihao zhong
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops Tom Lane
  • Re: [PG19] eager aggregation gives wrong results because of bpchar_ops shihao zhong
• Re: remove_useless_joins vs. bug #19560 Richard Guo
• Re: Remove invalid SS2/SS3 handling from EUC-KR routines SungJun Jang
• Re: stale comment in struct AlteredTableInfo David Rowley
• Re: Progress reporting: a debug trace and a test framework Manu
  • Re: Progress reporting: a debug trace and a test framework Michael Paquier
  • Progress reporting: a debug trace and a test framework Manu
• [PG19]pg_verifybackup never finishes on a gzip-compressed tar backup shihao zhong
  • Re: [PG19]pg_verifybackup never finishes on a gzip-compressed tar backup Chao Li
  • Re: [PG19]pg_verifybackup never finishes on a gzip-compressed tar backup shihao zhong
  • Re: [PG19]pg_verifybackup never finishes on a gzip-compressed tar backup Daniel Gustafsson
  • Re: [PG19]pg_verifybackup never finishes on a gzip-compressed tar backup Melanie Plageman
  • Re: [PG19]pg_verifybackup never finishes on a gzip-compressed tar backup Daniel Gustafsson
  • Re: [PG19]pg_verifybackup never finishes on a gzip-compressed tar backup Chao Li
  • Re: [PG19]pg_verifybackup never finishes on a gzip-compressed tar backup Andrew Dunstan
  • Re: [PG19]pg_verifybackup never finishes on a gzip-compressed tar backup Andrew Dunstan
  • Re: [PG19]pg_verifybackup never finishes on a gzip-compressed tar backup Daniel Gustafsson
  • Re: [PG19]pg_verifybackup never finishes on a gzip-compressed tar backup Andrew Dunstan
• Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers Masahiko Sawada
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers Masahiko Sawada
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers shihao zhong
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers Masahiko Sawada
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers shihao zhong
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers Bharath Rupireddy
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers Masahiko Sawada
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers Bharath Rupireddy
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers Masahiko Sawada
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers Bharath Rupireddy
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers Masahiko Sawada
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers Bharath Rupireddy
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers Masahiko Sawada
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers Bharath Rupireddy
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers Masahiko Sawada
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers Masahiko Sawada
  • Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers shihao zhong
• Re: issues with eager aggregation Richard Guo
  • Re: issues with eager aggregation Andrei Lepikhov
• Re: [BUG?] check_exclusion_or_unique_constraint false negative Mihail Nikalayeu
• Re: [PG19] plpgsql: SELECT INTO sets FOUND wrongly after a function becomes a SRF Tom Lane
  • Re: [PG19] plpgsql: SELECT INTO sets FOUND wrongly after a function becomes a SRF shihao zhong
• Re: Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates Mihail Nikalayeu
  • Re: Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates Manu
  • Re: Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates Manu
  • RE: Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates Hayato Kuroda (Fujitsu)
  • Re: Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates Zsolt Parragi
  • Re: Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates Mihail Nikalayeu
  • Re: Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates Manu
• Re: pg_resetwal: refuse to run when backup_label exists Michael Paquier
  • Re: pg_resetwal: refuse to run when backup_label exists Joao Detomini
  • Re: pg_resetwal: refuse to run when backup_label exists Tình Trần
  • Re: pg_resetwal: refuse to run when backup_label exists shihao zhong
  • Re: pg_resetwal: refuse to run when backup_label exists Tình Trần
• Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Masahiko Sawada
  • Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation shveta malik
  • Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Masahiko Sawada
  • Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Masahiko Sawada
  • Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation shveta malik
  • Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Masahiko Sawada
  • Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Fujii Masao
  • Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Masahiko Sawada
  • Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation shveta malik
  • Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Masahiko Sawada
  • Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Alexander Lakhin
  • RE: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Hayato Kuroda (Fujitsu)
  • RE: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Hayato Kuroda (Fujitsu)
  • Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Masahiko Sawada
  • RE: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Hayato Kuroda (Fujitsu)
  • Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Masahiko Sawada
  • RE: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Hayato Kuroda (Fujitsu)
  • Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation Masahiko Sawada
• 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: Limiting WAL retained for archiving, like max_slot_wal_keep_size surya poondla
• two small tab-completion patches (ALTER CONSTRAINT, CHECK modifiers) Baji Shaik
  • Re: two small tab-completion patches (ALTER CONSTRAINT, CHECK modifiers) Baji Shaik
  • Re: two small tab-completion patches (ALTER CONSTRAINT, CHECK modifiers) Chao Li
  • Re: two small tab-completion patches (ALTER CONSTRAINT, CHECK modifiers) Baji Shaik
  • Re: two small tab-completion patches (ALTER CONSTRAINT, CHECK modifiers) surya poondla
  • Re: two small tab-completion patches (ALTER CONSTRAINT, CHECK modifiers) Baji Shaik
  • Re: two small tab-completion patches (ALTER CONSTRAINT, CHECK modifiers) surya poondla
  • Re: two small tab-completion patches (ALTER CONSTRAINT, CHECK modifiers) Baji Shaik
• Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Sami Imseih
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Sami Imseih
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Michael Paquier
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Sami Imseih
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Michael Paquier
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Sami Imseih
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Michael Paquier
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Sami Imseih
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Michael Paquier
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Sami Imseih
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Zsolt Parragi
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Sami Imseih
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Michael Paquier
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Zsolt Parragi
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Sami Imseih
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Tom Lane
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Sami Imseih
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Michael Paquier
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Alexander Lakhin
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Michael Paquier
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Alexander Lakhin
• Re: [PG19] COPY (query) TO ... (FORMAT json) uses the table's column names Andrew Dunstan
  • Re: [PG19] COPY (query) TO ... (FORMAT json) uses the table's column names Joao Detomini
  • Re: [PG19] COPY (query) TO ... (FORMAT json) uses the table's column names shihao zhong
  • Re: [PG19] COPY (query) TO ... (FORMAT json) uses the table's column names Andrew Dunstan
  • Re: [PG19] COPY (query) TO ... (FORMAT json) uses the table's column names Melanie Plageman
  • Re: [PG19] COPY (query) TO ... (FORMAT json) uses the table's column names Andrew Dunstan
  • Re: [PG19] COPY (query) TO ... (FORMAT json) uses the table's column names Andrew Dunstan
• Re: pg_*_advice: tsv load failure, etc. Robert Haas
  • Re: pg_*_advice: tsv load failure, etc. Robert Haas
  • Re: pg_*_advice: tsv load failure, etc. Dongpo Liu
  • Re: pg_*_advice: tsv load failure, etc. Jakub Wartak
  • Re: pg_*_advice: tsv load failure, etc. Robert Haas
  • Re: pg_*_advice: tsv load failure, etc. Zsolt Parragi
  • Re: pg_*_advice: tsv load failure, etc. Dongpo Liu
  • Re: pg_*_advice: tsv load failure, etc. Robert Haas
  • Re: pg_*_advice: tsv load failure, etc. Robert Haas
  • Re: pg_*_advice: tsv load failure, etc. Robert Haas
  • Re: pg_*_advice: tsv load failure, etc. Alexander Lakhin
  • Re: pg_*_advice: tsv load failure, etc. Robert Haas
  • Re: pg_*_advice: tsv load failure, etc. Nikolay Samokhvalov
  • Re: pg_*_advice: tsv load failure, etc. Robert Haas
  • Re: pg_*_advice: tsv load failure, etc. Nikolay Samokhvalov
  • Re: pg_*_advice: tsv load failure, etc. Jakub Wartak
  • Re: pg_*_advice: tsv load failure, etc. Dongpo Liu
  • Re: pg_*_advice: tsv load failure, etc. Robert Haas
• Re: Add counted_by attribute Peter Eisentraut
  • Re: Add counted_by attribute Tristan Partin
  • Re: Add counted_by attribute Peter Eisentraut
• Re: [PATCH v1] Fix races in Windows pthread emulation Harrison Booth
• Re: Report relation extension blockers within parallel lock groups Nathan Bossart
• Re: UNDO with constant time recovery (CTR) Greg Burd
  • Re: UNDO with constant time recovery (CTR) Greg Burd
  • Re: UNDO with constant time recovery (CTR) Matthias van de Meent
  • Re: UNDO with constant time recovery (CTR) Greg Burd
  • Re: UNDO with constant time recovery (CTR) Matthias van de Meent
  • Re: UNDO with constant time recovery (CTR) Greg Burd

• Later messages