pgsql-hackers  

Messages by Thread

• • Re: Suggestion to add --continue-client-on-abort option to pgbench Yugo Nagata
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Rintaro Ikeda
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Yugo Nagata
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Rintaro Ikeda
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Yugo Nagata
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Rintaro Ikeda
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Yugo Nagata
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Yugo Nagata
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Yugo Nagata
• Re: alter check constraint enforceability jian he
• Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Fujii Masao
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Masahiro Ikeda
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Fujii Masao
• Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Hannu Krosing
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Nikita Malakhov
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Michael Paquier
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Nikita Malakhov
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Burd, Greg
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Nikita Malakhov
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Hannu Krosing
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Álvaro Herrera
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Hannu Krosing
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Nikita Malakhov
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Michael Paquier
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Nikita Malakhov
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Hannu Krosing
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Michael Paquier
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Nikhil Kumar Veldanda
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Nikhil Kumar Veldanda
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Hannu Krosing
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Nikita Malakhov
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Nikita Malakhov
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Michael Paquier
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Michael Paquier
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Nikita Malakhov
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Hannu Krosing
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Michael Paquier
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Hannu Krosing
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Nikita Malakhov
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Michael Paquier
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Michael Paquier
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Michael Paquier
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Jim Nasby
• Remove unused wait_event_info parameter in FileStartReadV() Bertrand Drouvot
  • Re: Remove unused wait_event_info parameter in FileStartReadV() Aleksander Alekseev
  • Re: Remove unused wait_event_info parameter in FileStartReadV() Bertrand Drouvot
• Wrong off type in smgrfd and mdfd 邱宇航
• Assertion failure during initdb with transaction_timeout set Fujii Masao
  • Re: Assertion failure during initdb with transaction_timeout set Tom Lane
  • Re: Assertion failure during initdb with transaction_timeout set Fujii Masao
• Re: Add 64-bit XIDs into PostgreSQL 15 Andrey Borodin
  • Re: Add 64-bit XIDs into PostgreSQL 15 Yura Sokolov
  • Re: Add 64-bit XIDs into PostgreSQL 15 Yura Sokolov
  • Re: Add 64-bit XIDs into PostgreSQL 15 Maksim.Melnikov
  • Re: Add 64-bit XIDs into PostgreSQL 15 Daniil Davydov
  • Re: Add 64-bit XIDs into PostgreSQL 15 Yura Sokolov
  • Re: Add 64-bit XIDs into PostgreSQL 15 Evgeny Voropaev
• Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment Ilia Evdokimov
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment Andrei Lepikhov
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment Ilia Evdokimov
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment David Rowley
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment Andrei Lepikhov
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment David Rowley
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment Andrei Lepikhov
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment Ilia Evdokimov
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment David Rowley
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment Lukas Fittl
• amcheck: Remove unused IndexCheckableCallback typedef Fujii Masao
  • Re: amcheck: Remove unused IndexCheckableCallback typedef Andrey Borodin
  • Re: amcheck: Remove unused IndexCheckableCallback typedef Fujii Masao
• Re: Adding pg_dump flag for parallel export to pipes Hannu Krosing
• Non-blocking archiver process Ronan Dunklau
  • Re: Non-blocking archiver process Noah Misch
  • Re: Non-blocking archiver process Patrick Stählin
• Re: Avoid possible dereference null pointer (contrib/postgres_fdw/postgres_fdw.c) Etsuro Fujita
  • Re: Avoid possible dereference null pointer (contrib/postgres_fdw/postgres_fdw.c) Etsuro Fujita
• Re: Emitting JSON to file using COPY TO jian he
• Re: proposal: plpgsql, new check for extra_errors - strict_expr_check Pavel Stehule
  • Re: proposal: plpgsql, new check for extra_errors - strict_expr_check Kirk Wolak
  • Re: proposal: plpgsql, new check for extra_errors - strict_expr_check Pavel Stehule
• Fix deprecation warning with libxml2 2.14 in contrib/xml2/ Michael Paquier
  • Re: Fix deprecation warning with libxml2 2.14 in contrib/xml2/ Michael Paquier
  • Re: Fix deprecation warning with libxml2 2.14 in contrib/xml2/ Tom Lane
  • Re: Fix deprecation warning with libxml2 2.14 in contrib/xml2/ Michael Paquier
  • Re: Fix deprecation warning with libxml2 2.14 in contrib/xml2/ Jim Jones
• Re: Pathify RHS unique-ification for semijoin planning Richard Guo
  • Re: Pathify RHS unique-ification for semijoin planning Álvaro Herrera
  • Re: Pathify RHS unique-ification for semijoin planning Richard Guo
  • Re: Pathify RHS unique-ification for semijoin planning Alexandra Wang
  • Re: Pathify RHS unique-ification for semijoin planning Richard Guo
  • Re: Pathify RHS unique-ification for semijoin planning Richard Guo
  • Re: Pathify RHS unique-ification for semijoin planning wenhui qiu
  • Re: Pathify RHS unique-ification for semijoin planning Richard Guo
  • Re: Pathify RHS unique-ification for semijoin planning Alexandra Wang
  • Re: Pathify RHS unique-ification for semijoin planning Richard Guo
• Re: Speedup truncations of temporary relation forks Fujii Masao
  • Re: Speedup truncations of temporary relation forks Daniil Davydov
• Re: COALESCE with single argument looks like identity function Tom Lane
• Re: [PATCH] Allow parallelism for plpgsql return expression after commit 556f7b7 Tom Lane
  • Re: [PATCH] Allow parallelism for plpgsql return expression after commit 556f7b7 Dilip Kumar
  • Re: [PATCH] Allow parallelism for plpgsql return expression after commit 556f7b7 Tom Lane
  • Re: [PATCH] Allow parallelism for plpgsql return expression after commit 556f7b7 Dilip Kumar
  • Re: [PATCH] Allow parallelism for plpgsql return expression after commit 556f7b7 Tom Lane
• Re: [PATCH] Fix hostaddr crash during non-blocking cancellation Tom Lane
  • Re: [PATCH] Fix hostaddr crash during non-blocking cancellation Jacob Champion
• Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL Alvaro Herrera
  • Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL Justin Pryzby
  • Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL Alvaro Herrera
  • Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL Tom Lane
  • Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL Alvaro Herrera
  • Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL Alvaro Herrera
  • Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL Alvaro Herrera
  • Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL Tom Lane
  • Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL Alvaro Herrera
  • Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL Álvaro Herrera
• Re: Add tab-completion for ALTER TABLE ADD NOT NULL Álvaro Herrera
• Improve error message for duplicate labels in enum types Yugo Nagata
  • Re: Improve error message for duplicate labels in enum types Rahila Syed
  • Re: Improve error message for duplicate labels in enum types Yugo Nagata
• Bloom Filter improvements in postgesql Ross Heaney
  • Re: Bloom Filter improvements in postgesql David E. Wheeler
  • Re: Bloom Filter improvements in postgesql Ross Heaney
  • Re: Bloom Filter improvements in postgesql Matthias van de Meent
  • Re: Bloom Filter improvements in postgesql Ross Heaney
• Re: Please update your contact list: It must be pgsql-hackers@lists.postgresql.org Álvaro Herrera
• Re: add tab-complete for ALTER DOMAIN ADD... Álvaro Herrera
• Re: Parallelize correlated subqueries that execute within each worker Andy Fan
• Re: CREATE DOMAIN create two not null constraints Álvaro Herrera
• use radix tree for bitmap heap scan John Naylor
• Re: Standardize the definition of the subtype field of AlterDomainStmt Michael Paquier
• Re: stats.sql might fail due to shared buffers also used by parallel tests Shlok Kyal
  • Re: stats.sql might fail due to shared buffers also used by parallel tests Alexander Lakhin
  • RE: stats.sql might fail due to shared buffers also used by parallel tests Hayato Kuroda (Fujitsu)
  • Re: stats.sql might fail due to shared buffers also used by parallel tests Alexander Lakhin
  • Re: stats.sql might fail due to shared buffers also used by parallel tests Yugo Nagata
  • Re: stats.sql might fail due to shared buffers also used by parallel tests Alexander Lakhin
  • RE: stats.sql might fail due to shared buffers also used by parallel tests Hayato Kuroda (Fujitsu)
  • Re: stats.sql might fail due to shared buffers also used by parallel tests Alexander Lakhin
  • Re: [Buildfarm:84] Re: stats.sql might fail due to shared buffers also used by parallel tests TAKATSUKA Haruka
  • Re: [Buildfarm:84] Re: stats.sql might fail due to shared buffers also used by parallel tests Alexander Lakhin
  • Re: [Buildfarm:84] Re: stats.sql might fail due to shared buffers also used by parallel tests TAKATSUKA Haruka
• Re: Improve verification of recovery_target_timeline GUC. Michael Paquier
  • Re: Improve verification of recovery_target_timeline GUC. David Steele
• Re: PG18 protocol version Tatsuo Ishii
  • Re: PG18 protocol version Jelte Fennema-Nio
  • Re: PG18 protocol version Tatsuo Ishii
• Re: MergeJoin beats HashJoin in the case of multiple hash clauses Tender Wang
  • Re: MergeJoin beats HashJoin in the case of multiple hash clauses Andrei Lepikhov
  • Re: MergeJoin beats HashJoin in the case of multiple hash clauses Tender Wang
  • Re: MergeJoin beats HashJoin in the case of multiple hash clauses Tender Wang
  • Re: MergeJoin beats HashJoin in the case of multiple hash clauses Tom Lane
  • Re: MergeJoin beats HashJoin in the case of multiple hash clauses Tender Wang
• Re: Add pg_get_injection_points() for information of injection points Michael Paquier
  • Re: Add pg_get_injection_points() for information of injection points Michael Paquier
  • Re: Add pg_get_injection_points() for information of injection points Rahila Syed
  • Re: Add pg_get_injection_points() for information of injection points Michael Paquier
  • Re: Add pg_get_injection_points() for information of injection points Michael Paquier
• Re: Persist injection points across server restarts Michael Paquier
• ACL identifier quoting has some issues Tom Lane
• Re: GIN tries to form a tuple with a partial compressedList during insertion Arseniy Mukhin
• RE: Proposal for optimizations with simd enabled sort Giacchino, Luca
• Re: Use RELATION_IS_OTHER_TEMP where possible Nathan Bossart
• [PATCH] Refactor bytea_sortsupport(), take two Aleksander Alekseev
• Re: problems with toast.* reloptions shihao zhong
  • Re: problems with toast.* reloptions Shayon Mukherjee
• [PATCH] plperl: use xsubpp -output unconditionally Dagfinn Ilmari Mannsåker
  • Re: [PATCH] plperl: use xsubpp -output unconditionally Daniel Gustafsson
• Re: gcc 15 "array subscript 0" warning at level -O3 jian he
  • Re: gcc 15 "array subscript 0" warning at level -O3 Andres Freund
  • Re: gcc 15 "array subscript 0" warning at level -O3 Andres Freund
• Re: Add progressive backoff to XactLockTableWait functions Fujii Masao
  • Re: Add progressive backoff to XactLockTableWait functions Andres Freund
  • Re: Add progressive backoff to XactLockTableWait functions Fujii Masao
  • Re: Add progressive backoff to XactLockTableWait functions Andres Freund
  • Re: Add progressive backoff to XactLockTableWait functions Fujii Masao
  • Re: Add progressive backoff to XactLockTableWait functions Xuneng Zhou
  • Re: Add progressive backoff to XactLockTableWait functions Xuneng Zhou
  • Re: Add progressive backoff to XactLockTableWait functions Fujii Masao
  • Re: Add progressive backoff to XactLockTableWait functions Andres Freund
  • Re: Add progressive backoff to XactLockTableWait functions Xuneng Zhou
  • Re: Add progressive backoff to XactLockTableWait functions Xuneng Zhou
  • Re: Add progressive backoff to XactLockTableWait functions Xuneng Zhou
  • Re: Add progressive backoff to XactLockTableWait functions Xuneng Zhou
  • Re: Add progressive backoff to XactLockTableWait functions Xuneng Zhou
  • Re: Add progressive backoff to XactLockTableWait functions Xuneng Zhou
  • Re: Add progressive backoff to XactLockTableWait functions Xuneng Zhou
• Re: Changing shared_buffers without restart Ashutosh Bapat
  • Re: Changing shared_buffers without restart Tomas Vondra
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Tomas Vondra
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Tomas Vondra
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Ashutosh Bapat
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Ashutosh Bapat
  • Re: Changing shared_buffers without restart Dmitry Dolgov

• Earlier messages
• Later messages