pgsql-hackers  

Messages by Thread

• • Re: ALTER TABLE ALTER CONSTRAINT misleading error message Álvaro Herrera
  • Re: ALTER TABLE ALTER CONSTRAINT misleading error message Fujii Masao
  • Re: ALTER TABLE ALTER CONSTRAINT misleading error message Álvaro Herrera
• Re: postmaster uses more CPU in 18 beta1 with io_method=io_uring Andres Freund
  • Re: postmaster uses more CPU in 18 beta1 with io_method=io_uring Jim Nasby
  • Re: postmaster uses more CPU in 18 beta1 with io_method=io_uring Andres Freund
  • Re: postmaster uses more CPU in 18 beta1 with io_method=io_uring Burd, Greg
  • Re: postmaster uses more CPU in 18 beta1 with io_method=io_uring Andres Freund
  • Re: postmaster uses more CPU in 18 beta1 with io_method=io_uring Andres Freund
• Re: Issue with custom operator in simple case Maxim Orlov
  • Re: Issue with custom operator in simple case David G. Johnston
• Re: New function normal_rand_array function to contrib/tablefunc. jian he
• array_random jian he
  • Re: array_random jian he
  • Re: array_random Vik Fearing
  • Re: array_random Dean Rasheed
  • Re: array_random jian he
  • Re: array_random Aleksander Alekseev
  • Re: array_random Dean Rasheed
  • Re: array_random jian he
  • Re: array_random Tom Lane
• Re: [PATCH] Fix OAuth feature detection on OpenBSD+Meson Jacob Champion
  • Re: [PATCH] Fix OAuth feature detection on OpenBSD+Meson Nazir Bilal Yavuz
  • Re: [PATCH] Fix OAuth feature detection on OpenBSD+Meson Nazir Bilal Yavuz
  • Re: [PATCH] Fix OAuth feature detection on OpenBSD+Meson Jacob Champion
• Re: AIO v2.5 Andres Freund
  • Re: AIO v2.5 Matthias van de Meent
  • Re: AIO v2.5 Andres Freund
  • Re: AIO v2.5 Matthias van de Meent
  • Re: AIO v2.5 Andres Freund
  • Re: AIO v2.5 Andres Freund
  • Re: AIO v2.5 Tomas Vondra
  • Re: AIO v2.5 Andres Freund
  • Re: AIO v2.5 Tomas Vondra
  • Re: AIO v2.5 Andres Freund
  • Re: AIO v2.5 Tomas Vondra
  • Re: AIO v2.5 Nathan Bossart
• Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Bertrand Drouvot
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Amit Kapila
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Amit Kapila
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Amit Kapila
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Amit Kapila
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Amit Kapila
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • RE: POC: enable logical decoding when wal_level = 'replica' without a server restart Hayato Kuroda (Fujitsu)
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart vignesh C
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • RE: POC: enable logical decoding when wal_level = 'replica' without a server restart Hayato Kuroda (Fujitsu)
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • RE: POC: enable logical decoding when wal_level = 'replica' without a server restart Hayato Kuroda (Fujitsu)
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Amit Kapila
• Adding wait events statistics Bertrand Drouvot
  • Re: Adding wait events statistics Michael Paquier
  • Re: Adding wait events statistics Bertrand Drouvot
  • Re: Adding wait events statistics Michael Paquier
  • Re: Adding wait events statistics Bertrand Drouvot
  • Re: Adding wait events statistics Bertrand Drouvot
  • Re: Adding wait events statistics Michael Paquier
  • Re: Adding wait events statistics Bertrand Drouvot
  • Re: Adding wait events statistics Andres Freund
  • Re: Adding wait events statistics Bertrand Drouvot
  • Re: Adding wait events statistics Andres Freund
  • Re: Adding wait events statistics Bertrand Drouvot
  • Re: Adding wait events statistics Andres Freund
  • Re: Adding wait events statistics Bertrand Drouvot
  • Re: Adding wait events statistics Bertrand Drouvot
  • Re: Adding wait events statistics Andres Freund
  • Re: Adding wait events statistics Bertrand Drouvot
  • Re: Adding wait events statistics Andres Freund
  • Re: Adding wait events statistics Bertrand Drouvot
  • Re: Adding wait events statistics Robert Haas
  • Re: Adding wait events statistics Bertrand Drouvot
  • Re: Adding wait events statistics Robert Haas
  • Re: Adding wait events statistics Bertrand Drouvot
  • Re: Adding wait events statistics Robert Haas
  • Re: Adding wait events statistics Bertrand Drouvot
• Re: add function for creating/attaching hash table in DSM registry Nathan Bossart
  • Re: add function for creating/attaching hash table in DSM registry Nathan Bossart
  • Re: add function for creating/attaching hash table in DSM registry Nathan Bossart
  • Re: add function for creating/attaching hash table in DSM registry Nathan Bossart
  • Re: add function for creating/attaching hash table in DSM registry Florents Tselai
• Re: Periodic FSM vacuum doesn't happen in one-pass strategy vacuum. Melanie Plageman
  • Re: Periodic FSM vacuum doesn't happen in one-pass strategy vacuum. Masahiko Sawada
  • Re: Periodic FSM vacuum doesn't happen in one-pass strategy vacuum. Masahiko Sawada
  • Re: Periodic FSM vacuum doesn't happen in one-pass strategy vacuum. Melanie Plageman
  • Re: Periodic FSM vacuum doesn't happen in one-pass strategy vacuum. Masahiko Sawada
• Re: pg_get_multixact_members not documented Sami Imseih
  • Re: pg_get_multixact_members not documented Nathan Bossart
  • Re: pg_get_multixact_members not documented Sami Imseih
  • Re: pg_get_multixact_members not documented Sami Imseih
  • Re: pg_get_multixact_members not documented Nathan Bossart
  • Re: pg_get_multixact_members not documented Nathan Bossart
  • Re: pg_get_multixact_members not documented Sami Imseih
  • Re: pg_get_multixact_members not documented Nathan Bossart
• Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Andres Freund
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Michael Paquier
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Michael Paquier
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Michael Paquier
  • Re: Improve error reporting in 027_stream_regress test Tom Lane
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Michael Paquier
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Michael Paquier
  • Re: Improve error reporting in 027_stream_regress test Andres Freund
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Alexander Lakhin
  • Re: Improve error reporting in 027_stream_regress test Tom Lane
  • Re: Improve error reporting in 027_stream_regress test Michael Paquier
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Tom Lane
• RE: Check for existing replication slot in pg_createsubscriber Hayato Kuroda (Fujitsu)
• Re: Improve explicit cursor handling in pg_stat_statements Sami Imseih
  • Re: Improve explicit cursor handling in pg_stat_statements Michael Paquier
• RE: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages Hayato Kuroda (Fujitsu)
  • Re: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages vignesh C
  • Re: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages Michael Paquier
  • RE: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages Hayato Kuroda (Fujitsu)
  • Re: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages Michael Paquier
  • Re: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages Alexander Korotkov
  • Re: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages Michael Paquier
  • Re: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages Alexander Korotkov
  • Re: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages Tom Lane
  • Re: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages Alexander Korotkov
  • Re: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages Tom Lane
  • Re: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages Michael Paquier
• Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Tom Lane
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Tom Lane
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Tom Lane
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov

• Earlier messages
• Later messages