pgsql-hackers  

Messages by Thread

• Avoid possible dereference null pointer (src/backend/utils/cache/relcache.c) Ranier Vilela
  • Re: Avoid possible dereference null pointer (src/backend/utils/cache/relcache.c) Aleksander Alekseev
  • Re: Avoid possible dereference null pointer (src/backend/utils/cache/relcache.c) Ranier Vilela
  • Re: Avoid possible dereference null pointer (src/backend/utils/cache/relcache.c) Aleksander Alekseev
  • Re: Avoid possible dereference null pointer (src/backend/utils/cache/relcache.c) Ranier Vilela
  • Re: Avoid possible dereference null pointer (src/backend/utils/cache/relcache.c) Tomas Vondra
  • Re: Avoid possible dereference null pointer (src/backend/utils/cache/relcache.c) Ranier Vilela
  • Re: Avoid possible dereference null pointer (src/backend/utils/cache/relcache.c) Aleksander Alekseev
  • Re: Avoid possible dereference null pointer (src/backend/utils/cache/relcache.c) Ranier Vilela
  • Re: Avoid possible dereference null pointer (src/backend/utils/cache/relcache.c) Daniel Gustafsson
• 回复: Fix potential overflow risks from wcscpy and sprintf Yan Haibo
  • Re: 回复: Fix potential overflow risks from wcscpy and sprintf Tom Lane
  • 回复: 回复: Fix potential overflow risks from wcscpy and sprintf Yan Haibo
  • Re: 回复: 回复: Fix potential overflow risks from wcscpy and sprintf Tom Lane
  • 回复: 回复: 回复: Fix potential overflow risks from wcscpy and sprintf Yan Haibo
  • 回复: Fix potential overflow risks from wcscpy and sprintf Yan Haibo
• Re: amcheck support for BRIN indexes Andrey Borodin
  • Re: amcheck support for BRIN indexes Arseniy Mukhin
  • Re: amcheck support for BRIN indexes Andrey Borodin
  • Re: amcheck support for BRIN indexes Arseniy Mukhin
  • Re: amcheck support for BRIN indexes Arseniy Mukhin
  • Re: amcheck support for BRIN indexes Álvaro Herrera
  • Re: amcheck support for BRIN indexes Tomas Vondra
  • Re: amcheck support for BRIN indexes Álvaro Herrera
  • Re: amcheck support for BRIN indexes Arseniy Mukhin
  • Re: amcheck support for BRIN indexes Tomas Vondra
  • Re: amcheck support for BRIN indexes Arseniy Mukhin
  • Re: amcheck support for BRIN indexes Arseniy Mukhin
• Returning nbtree posting list TIDs in DESC order during backwards scans Peter Geoghegan
  • Re: Returning nbtree posting list TIDs in DESC order during backwards scans Peter Geoghegan
  • Re: Returning nbtree posting list TIDs in DESC order during backwards scans Mircea Cadariu
  • Re: Returning nbtree posting list TIDs in DESC order during backwards scans Peter Geoghegan
  • Re: Returning nbtree posting list TIDs in DESC order during backwards scans Peter Geoghegan
  • Re: Returning nbtree posting list TIDs in DESC order during backwards scans Mircea Cadariu
• Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Sergey Sargsyan
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Mihail Nikalayeu
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Sergey Sargsyan
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Sergey Sargsyan
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Mihail Nikalayeu
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Sergey Sargsyan
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Mihail Nikalayeu
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Sergey Sargsyan
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Sergey Sargsyan
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Mihail Nikalayeu
• Re: psql: tab-completion support for COPY ... TO/FROM STDIN, STDOUT, and PROGRAM Yugo Nagata
  • Re: psql: tab-completion support for COPY ... TO/FROM STDIN, STDOUT, and PROGRAM Yugo Nagata
  • Re: psql: tab-completion support for COPY ... TO/FROM STDIN, STDOUT, and PROGRAM Yugo Nagata
• Re: Per-role disabling of LEAKPROOF requirements for row-level security? Yugo Nagata
  • Re: Per-role disabling of LEAKPROOF requirements for row-level security? Tom Lane
  • Re: Per-role disabling of LEAKPROOF requirements for row-level security? Nathan Bossart
  • Re: Per-role disabling of LEAKPROOF requirements for row-level security? Tom Lane
  • Re: Per-role disabling of LEAKPROOF requirements for row-level security? Nathan Bossart
  • Re: Per-role disabling of LEAKPROOF requirements for row-level security? Andreas Lind
  • Re: Per-role disabling of LEAKPROOF requirements for row-level security? Jelte Fennema-Nio
  • Re: Per-role disabling of LEAKPROOF requirements for row-level security? Yugo Nagata
• Re: CHECKPOINT unlogged data Christoph Berg
  • Re: CHECKPOINT unlogged data Nathan Bossart
  • Re: CHECKPOINT unlogged data Christoph Berg
  • Re: CHECKPOINT unlogged data Nathan Bossart
  • Re: CHECKPOINT unlogged data Christoph Berg
  • Re: CHECKPOINT unlogged data Nathan Bossart
  • Re: CHECKPOINT unlogged data Christoph Berg
  • Re: CHECKPOINT unlogged data Fujii Masao
  • Re: CHECKPOINT unlogged data Dilip Kumar
  • Re: CHECKPOINT unlogged data Dilip Kumar
  • Re: CHECKPOINT unlogged data Dilip Kumar
  • Re: CHECKPOINT unlogged data Nathan Bossart
  • Re: CHECKPOINT unlogged data Dilip Kumar
  • Re: CHECKPOINT unlogged data Nathan Bossart
  • Re: CHECKPOINT unlogged data Dilip Kumar
  • Re: CHECKPOINT unlogged data Nathan Bossart
• Re: Read-Write optimistic lock (Re: sinvaladt.c: remove msgnumLock, use atomic operations on maxMsgNum) Yura Sokolov
  • Re: Read-Write optimistic lock (Re: sinvaladt.c: remove msgnumLock, use atomic operations on maxMsgNum) Andres Freund
  • Re: Read-Write optimistic lock (Re: sinvaladt.c: remove msgnumLock, use atomic operations on maxMsgNum) Sergey Shinderuk
  • Re: Read-Write optimistic lock (Re: sinvaladt.c: remove msgnumLock, use atomic operations on maxMsgNum) Andres Freund
  • Re: Read-Write optimistic lock (Re: sinvaladt.c: remove msgnumLock, use atomic operations on maxMsgNum) Yura Sokolov
  • Re: Read-Write optimistic lock (Re: sinvaladt.c: remove msgnumLock, use atomic operations on maxMsgNum) Andres Freund
• Re: Add XMLNamespaces to XMLElement Jim Jones
  • Re: Add XMLNamespaces to XMLElement Jim Jones
• Re: Commitfest app release at half June Jelte Fennema-Nio
• [PATCH] Add an ldflags_sl meson build option Matt Smith (matts3)
  • Re: [PATCH] Add an ldflags_sl meson build option Peter Eisentraut
  • Re: [PATCH] Add an ldflags_sl meson build option Matt Smith (matts3)
  • Re: [PATCH] Add an ldflags_sl meson build option Peter Eisentraut
  • Re: [PATCH] Add an ldflags_sl meson build option Matt Smith (matts3)
  • Re: [PATCH] Add an ldflags_sl meson build option Peter Eisentraut
  • Re: [PATCH] Add an ldflags_sl meson build option Matt Smith (matts3)
  • Re: [PATCH] Add an ldflags_sl meson build option Peter Eisentraut
  • Re: [PATCH] Add an ldflags_sl meson build option Nazir Bilal Yavuz
  • Re: [PATCH] Add an ldflags_sl meson build option Matt Smith (matts3)
• [PATCH] Remove unused #include's in src/backend/utils/adt/* Aleksander Alekseev
  • Re: [PATCH] Remove unused #include's in src/backend/utils/adt/* Tom Lane
  • Re: [PATCH] Remove unused #include's in src/backend/utils/adt/* Aleksander Alekseev
  • Re: [PATCH] Remove unused #include's in src/backend/utils/adt/* Peter Eisentraut
• Re: [PATCH] Split varlena.c into varlena.c and bytea.c Aleksander Alekseev
  • Re: [PATCH] Split varlena.c into varlena.c and bytea.c Michael Paquier
  • Re: [PATCH] Split varlena.c into varlena.c and bytea.c Aleksander Alekseev
  • Re: [PATCH] Split varlena.c into varlena.c and bytea.c Michael Paquier
• Re: Init connection time grows quadratically Потапов Александр
• No error checking when reading from file using zstd in pg_dump Evgeniy Gorbanev
  • Re: No error checking when reading from file using zstd in pg_dump Daniel Gustafsson
  • Re: No error checking when reading from file using zstd in pg_dump Evgeniy Gorbanev
  • Re: No error checking when reading from file using zstd in pg_dump Daniel Gustafsson
  • Re: No error checking when reading from file using zstd in pg_dump Evgeniy Gorbanev
  • Re: No error checking when reading from file using zstd in pg_dump Daniel Gustafsson
  • Re: No error checking when reading from file using zstd in pg_dump Evgeniy Gorbanev
  • Re: No error checking when reading from file using zstd in pg_dump Tom Lane
  • Re: No error checking when reading from file using zstd in pg_dump Daniel Gustafsson
  • Re: No error checking when reading from file using zstd in pg_dump Tom Lane
  • Re: No error checking when reading from file using zstd in pg_dump Daniel Gustafsson
  • Re: No error checking when reading from file using zstd in pg_dump Tom Lane
  • Re: No error checking when reading from file using zstd in pg_dump Tomas Vondra
  • Re: No error checking when reading from file using zstd in pg_dump Tom Lane
  • Re: No error checking when reading from file using zstd in pg_dump Daniel Gustafsson
  • Re: No error checking when reading from file using zstd in pg_dump Tom Lane
  • Re: No error checking when reading from file using zstd in pg_dump Daniel Gustafsson
  • Re: No error checking when reading from file using zstd in pg_dump Tom Lane
  • Re: No error checking when reading from file using zstd in pg_dump Daniel Gustafsson
  • Re: No error checking when reading from file using zstd in pg_dump Daniel Gustafsson
  • Re: No error checking when reading from file using zstd in pg_dump Tomas Vondra
  • Re: No error checking when reading from file using zstd in pg_dump Daniel Gustafsson
  • Re: No error checking when reading from file using zstd in pg_dump Tom Lane
  • Re: No error checking when reading from file using zstd in pg_dump Daniel Gustafsson
  • Re: No error checking when reading from file using zstd in pg_dump Tomas Vondra
  • Re: No error checking when reading from file using zstd in pg_dump Daniel Gustafsson
• Re: Possibly hard-to-read message Daniel Gustafsson
• relrewrite not documented at the top of heap_create_with_catalog() Michael Paquier
  • Re: relrewrite not documented at the top of heap_create_with_catalog() Steven Niu
  • Re: relrewrite not documented at the top of heap_create_with_catalog() Yugo Nagata
  • Re: relrewrite not documented at the top of heap_create_with_catalog() Michael Paquier
  • Re: relrewrite not documented at the top of heap_create_with_catalog() Yugo Nagata
• Re: Add enable_groupagg GUC parameter to control GroupAggregate usage David Rowley
  • Re: Add enable_groupagg GUC parameter to control GroupAggregate usage Tatsuro Yamada
• Re: [PATCH v2] parallel pg_restore: move offset-building phase to before forking Dimitrios Apostolou
• [WIP PATCH v3] Implement "pg_restore --data-only --clean" as a way to skip WAL Dimitrios Apostolou
  • Re: [WIP PATCH v3] Implement "pg_restore --data-only --clean" as a way to skip WAL Dimitrios Apostolou
• Question about RWF_DONTCACHE Jinliang Zheng
• Re: Amcheck verification of GiST and GIN Andrey Borodin
  • Re: Amcheck verification of GiST and GIN Arseniy Mukhin
  • Re: Amcheck verification of GiST and GIN Tomas Vondra
  • Re: Amcheck verification of GiST and GIN Arseniy Mukhin
  • Re: Amcheck verification of GiST and GIN Tomas Vondra
  • Re: Amcheck verification of GiST and GIN Thom Brown
  • Re: Amcheck verification of GiST and GIN Tomas Vondra
• Re: Sanding down some edge cases for PL/pgSQL reserved words Pavel Stehule
  • Re: Sanding down some edge cases for PL/pgSQL reserved words Tom Lane
• Re: [PATCH] PGSERVICEFILE as part of a normal connection string Ryo Kanbayashi
  • Re: [PATCH] PGSERVICEFILE as part of a normal connection string Michael Paquier
  • Re: [PATCH] PGSERVICEFILE as part of a normal connection string Ryo Kanbayashi
  • Re: [PATCH] PGSERVICEFILE as part of a normal connection string Michael Paquier
  • Re: [PATCH] PGSERVICEFILE as part of a normal connection string Michael Paquier
  • Re: [PATCH] PGSERVICEFILE as part of a normal connection string Michael Paquier
  • Re: [PATCH] PGSERVICEFILE as part of a normal connection string Ryo Kanbayashi
• Re: Psql meta-command conninfo+ Peter Eisentraut
• Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Lakhin
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Lakhin
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Tom Lane
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly vignesh C
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Amit Kapila
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly vignesh C
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Zhijie Hou (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Dilip Kumar
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Dilip Kumar
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Dilip Kumar
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Amit Kapila
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Amit Kapila
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Tom Lane
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly vignesh C
• [PATCH] Fix incomplete memory clearing in OAuth authentication Taras Kloba
  • Re: [PATCH] Fix incomplete memory clearing in OAuth authentication Daniel Gustafsson
• Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Florents Tselai
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler

• Earlier messages
• Later messages