agora inbox for pgsql-hackers@postgresql.org
help / color / mirror / Atom feedAdding comments to extension objects
2026-08-08 13:17 UTC Bruce Momjian <bruce@momjian.us>
` Re: Adding comments to extension objects
2026-08-08 22:12 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Adding comments to extension objects
2026-08-08 23:48 UTC Bruce Momjian <bruce@momjian.us>
[3+ messages in thread]
[PATCH 3/6] Add primary_slot_name to init_from_backup in TAP test.
2018-12-19 03:43 UTC Kyotaro Horiguchi <horiguchi.kyotaro@lab.ntt.co.jp>
` [PATCH v29 03/11] Allow to prolong life span of transition tables until transaction end
2019-12-20 01:09 UTC Yugo Nagata <nagata@sraoss.co.jp>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-06 12:19 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-13 15:15 UTC jian he <jian.universality@gmail.com>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-13 17:30 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-14 23:13 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-15 05:08 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-15 15:30 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-21 20:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-25 12:15 UTC Chengpeng Yan <chengpeng_yan@outlook.com>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-25 14:34 UTC Tomas Vondra <tomas@vondra.me>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-25 15:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-27 17:49 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-27 19:08 UTC Tomas Vondra <tomas@vondra.me>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-27 20:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-27 22:02 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-28 01:29 UTC Tomas Vondra <tomas@vondra.me>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-05-28 19:03 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-06-22 19:03 UTC Tomas Vondra <tomas@vondra.me>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-06-23 11:02 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-07-03 11:51 UTC Tomas Vondra <tomas@vondra.me>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-07-16 09:18 UTC Ilia Evdokimov <ilya.evdokimov@tantorlabs.com>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-07-27 19:41 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-08-03 23:06 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: Is there value in having optimizer stats for joins/foreignkeys?
2026-08-08 22:08 UTC Tomas Vondra <tomas@vondra.me>
[25+ messages in thread]
[PATCH] Avoid touching user indexes while they are being (re)built.
2019-09-12 14:35 UTC Arseny Sher <sher-ars@yandex.ru>
` [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-09 20:45 UTC SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-11 03:01 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-21 06:49 UTC vignesh C <vignesh21@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-21 14:38 UTC SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-22 09:15 UTC shveta malik <shveta.malik@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-25 07:12 UTC SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-25 09:58 UTC shveta malik <shveta.malik@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-25 19:01 UTC SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-26 04:36 UTC shveta malik <shveta.malik@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-26 05:50 UTC shveta malik <shveta.malik@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-26 08:11 UTC SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-27 03:53 UTC shveta malik <shveta.malik@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-27 04:31 UTC SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-27 08:11 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-27 10:59 UTC shveta malik <shveta.malik@gmail.com>
` RE: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-27 11:46 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-27 12:10 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-28 01:08 UTC SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-28 01:11 UTC SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-29 04:17 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-29 05:11 UTC SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
` RE: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-29 05:36 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-29 05:45 UTC shveta malik <shveta.malik@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-06-10 04:06 UTC SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-06-10 06:14 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-06-16 23:27 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-07-30 19:12 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-07-31 04:40 UTC shveta malik <shveta.malik@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-08-03 05:27 UTC shveta malik <shveta.malik@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-08-04 02:20 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` RE: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-08-04 08:39 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-08-04 10:28 UTC shveta malik <shveta.malik@gmail.com>
` RE: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-08-04 10:56 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-08-04 11:16 UTC shveta malik <shveta.malik@gmail.com>
` RE: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-08-04 11:33 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-08-05 03:36 UTC shveta malik <shveta.malik@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-08-05 18:15 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-08-06 03:46 UTC shveta malik <shveta.malik@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-08-06 08:02 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-08-06 12:26 UTC Ashutosh Sharma <ashu.coek88@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-08-06 19:20 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-08-08 21:17 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
[43+ messages in thread]
[PATCH v3 6/7] Row pattern recognition patch (tests).
2023-07-26 10:49 UTC Tatsuo Ishii <ishii@postgresql.org>
` WAL compression setting after PostgreSQL LZ4 default change
2026-06-30 10:25 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-06-30 10:51 UTC Christoph Berg <myon@debian.org>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-06-30 13:48 UTC Japin Li <japinli@hotmail.com>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-06-30 23:45 UTC Michael Paquier <michael@paquier.xyz>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-01 01:53 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-03 02:18 UTC Japin Li <japinli@hotmail.com>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-03 02:58 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-03 08:38 UTC Japin Li <japinli@hotmail.com>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-07 22:26 UTC Michael Paquier <michael@paquier.xyz>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-07 22:46 UTC Jelte Fennema-Nio <postgres@jeltef.nl>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-07 22:58 UTC Christoph Berg <myon@debian.org>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-08 06:37 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-16 15:00 UTC Tomas Vondra <tomas@vondra.me>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-16 15:08 UTC Andres Freund <andres@anarazel.de>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-16 22:00 UTC Michael Paquier <michael@paquier.xyz>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-18 20:28 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-20 06:23 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-31 12:35 UTC Christoph Berg <myon@debian.org>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-31 12:55 UTC Tomas Vondra <tomas@vondra.me>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-31 13:04 UTC Tomas Vondra <tomas@vondra.me>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-31 13:10 UTC Christoph Berg <myon@debian.org>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-31 14:58 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-31 15:50 UTC Christoph Berg <myon@debian.org>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-31 21:44 UTC Tomas Vondra <tomas@vondra.me>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-07-31 22:50 UTC Christoph Berg <myon@debian.org>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-08-01 01:44 UTC Japin Li <japinli@hotmail.com>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-08-01 08:42 UTC Michael Paquier <michael@paquier.xyz>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-08-03 08:26 UTC Andreas Karlsson <andreas@proxel.se>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-08-03 13:36 UTC Hannu Krosing <hannuk@google.com>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-08-03 20:36 UTC Tomas Vondra <tomas@vondra.me>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-08-04 07:03 UTC Hannu Krosing <hannuk@google.com>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-08-04 10:01 UTC Tomas Vondra <tomas@vondra.me>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-08-04 11:15 UTC Hannu Krosing <hannuk@google.com>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-08-06 12:11 UTC Tomas Vondra <tomas@vondra.me>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-08-06 14:31 UTC Hannu Krosing <hannuk@google.com>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-08-06 14:50 UTC Ken Marshall <ktm@rice.edu>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-08-06 15:32 UTC Tomas Vondra <tomas@vondra.me>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-08-08 19:30 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: WAL compression setting after PostgreSQL LZ4 default change
2026-08-08 20:57 UTC Jelte Fennema-Nio <postgres@jeltef.nl>
[40+ messages in thread]
[PATCH v20 7/8] Row pattern recognition patch (tests).
2024-05-24 02:26 UTC Tatsuo Ishii <ishii@postgresql.org>
` postgres_fdw: Emit message when batch_size is reduced
2026-06-01 11:55 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-06-05 05:43 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-06-05 11:02 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-06-05 17:43 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-06-05 17:52 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-06-09 11:29 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-06-09 11:38 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-06-09 20:00 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-06-09 20:22 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-06-10 09:08 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-06-16 20:19 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-06-19 12:38 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-06-22 20:40 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-06-23 09:47 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-07-11 18:26 UTC Nurlan Tulemisov <nurlan.tulemisov@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-07-16 07:50 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-07-17 13:09 UTC Nurlan Tulemisov <nurlan.tulemisov@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-07-20 09:16 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-07-21 15:16 UTC Nurlan Tulemisov <nurlan.tulemisov@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-07-22 09:47 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: postgres_fdw: Emit message when batch_size is reduced
2026-08-08 19:29 UTC solai v <solai.cdac@gmail.com>
[22+ messages in thread]
Re: Random 038_walsnd_shutdown_timeout.pl failure on goldfish
2026-08-08 13:11 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: Random 038_walsnd_shutdown_timeout.pl failure on goldfish
2026-08-08 19:26 UTC Daniel Gustafsson <daniel@yesql.se>
[2+ messages in thread]
comment/security label for publication/subscription
2017-03-24 04:18 UTC Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
` Re: comment/security label for publication/subscription
2017-03-24 20:52 UTC Robert Haas <robertmhaas@gmail.com>
` Re: comment/security label for publication/subscription
2017-03-24 20:56 UTC Stephen Frost <sfrost@snowman.net>
` [PATCH v22 1/8] Row pattern recognition patch for raw parser.
2024-09-19 04:48 UTC Tatsuo Ishii <ishii@postgresql.org>
` Re: [HACKERS] comment/security label for publication/subscription
2026-08-08 17:35 UTC Andres Freund <andres@anarazel.de>
[5+ messages in thread]
[PATCH v4] Add argument names to multi-argument aggregates
2023-02-27 13:06 UTC Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
` [PATCH] Use wait_classes.h in pg_prewarm
2026-06-27 11:15 UTC Dongpo Liu <poe.liu@pm.me>
` Re: [PATCH] Use wait_classes.h in pg_prewarm
2026-08-08 15:33 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: [PATCH] Use wait_classes.h in pg_prewarm
2026-08-08 15:45 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: [PATCH] Use wait_classes.h in pg_prewarm
2026-08-08 15:51 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
[5+ messages in thread]
[PATCH v5 2/8] Documentation
2019-05-18 18:07 UTC David Fetter <david@fetter.org>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-02-24 19:48 UTC Mihail Nikalayeu <mihailnikalayeu@gmail.com>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-03-09 00:09 UTC Mihail Nikalayeu <mihailnikalayeu@gmail.com>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-03-23 22:08 UTC Mihail Nikalayeu <mihailnikalayeu@gmail.com>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-03-28 19:17 UTC Mihail Nikalayeu <mihailnikalayeu@gmail.com>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-03-31 22:11 UTC Mihail Nikalayeu <mihailnikalayeu@gmail.com>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-04-06 18:21 UTC Mihail Nikalayeu <mihailnikalayeu@gmail.com>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-04-07 01:42 UTC Josh Kupershmidt <schmiddy@gmail.com>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-04-07 23:19 UTC Mihail Nikalayeu <mihailnikalayeu@gmail.com>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-04-11 16:56 UTC Mihail Nikalayeu <mihailnikalayeu@gmail.com>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-04-13 01:05 UTC Josh Kupershmidt <schmiddy@gmail.com>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-06-29 21:48 UTC Mihail Nikalayeu <mihailnikalayeu@gmail.com>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-08-05 20:01 UTC Matthias van de Meent <boekewurm+postgres@gmail.com>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-08-06 10:08 UTC Mihail Nikalayeu <mihailnikalayeu@gmail.com>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-08-08 15:03 UTC Mihail Nikalayeu <mihailnikalayeu@gmail.com>
[15+ messages in thread]
[PATCH v2] Cast result of copyObject() to correct type
2017-02-28 20:07 UTC Peter Eisentraut <peter_e@gmx.net>
` Allow pg_read_all_stats to read replication origin status
2026-08-08 14:46 UTC Virender Singla <virender.cse@gmail.com>
[2+ messages in thread]
[PATCH v6 5/7] Refactor for consistency/symmetry
2020-02-09 21:08 UTC Justin Pryzby <pryzbyj@telsasoft.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-05-20 16:26 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-05-25 14:20 UTC Vitaly Davydov <v.davydov@postgrespro.ru>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-05-26 15:01 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-05 11:58 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-09 16:18 UTC Vitaly Davydov <v.davydov@postgrespro.ru>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-10 08:42 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-12 06:00 UTC Vitaly Davydov <v.davydov@postgrespro.ru>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-12 09:23 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-18 02:48 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-18 13:11 UTC Vitaly Davydov <v.davydov@postgrespro.ru>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-18 16:22 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-22 18:32 UTC Vitaly Davydov <v.davydov@postgrespro.ru>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-23 03:13 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-24 15:16 UTC Vitaly Davydov <v.davydov@postgrespro.ru>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-25 12:14 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-25 13:36 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-26 09:31 UTC Vitaly Davydov <v.davydov@postgrespro.ru>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-27 06:11 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-06-30 03:14 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-07-01 15:57 UTC Vitaly Davydov <v.davydov@postgrespro.ru>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-07-02 09:31 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-08-04 05:30 UTC JoongHyuk Shin <sjh910805@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-08-04 11:16 UTC Vitaly Davydov <v.davydov@postgrespro.ru>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-08-05 02:40 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-08-05 08:10 UTC Vitaly Davydov <v.davydov@postgrespro.ru>
` Re: Deadlock detector fails to activate on a hot standby replica
2026-08-08 13:51 UTC Xuneng Zhou <xunengzhou@gmail.com>
[27+ messages in thread]
[PATCH v5 1/1] Fix authorization check for role membership changes.
2026-08-07 21:50 UTC Nathan Bossart <nathan@postgresql.org>
[PATCH v5 1/1] Fix authorization check for role membership changes.
2026-08-07 21:50 UTC Nathan Bossart <nathan@postgresql.org>
[PATCH v5 1/1] Fix authorization check for role membership changes.
2026-08-07 21:50 UTC Nathan Bossart <nathan@postgresql.org>
[PATCH v11 04/17] BitmapPrefetch use prefetch block recheck for skip fetch
2024-02-13 00:03 UTC Melanie Plageman <melanieplageman@gmail.com>
` [PATCH v5 1/1] Fix authorization check for role membership changes.
2026-08-07 21:50 UTC Nathan Bossart <nathan@postgresql.org>
[2+ messages in thread]
[PATCH v5 1/1] Fix authorization check for role membership changes.
2026-08-07 21:50 UTC Nathan Bossart <nathan@postgresql.org>
[PATCH v5 1/1] Fix authorization check for role membership changes.
2026-08-07 21:50 UTC Nathan Bossart <nathan@postgresql.org>
[PATCH v5 1/1] Fix authorization check for role membership changes.
2026-08-07 21:50 UTC Nathan Bossart <nathan@postgresql.org>
[PATCH v5 1/1] Fix authorization check for role membership changes.
2026-08-07 21:50 UTC Nathan Bossart <nathan@postgresql.org>
[PATCH v5 1/1] Fix authorization check for role membership changes.
2026-08-07 21:50 UTC Nathan Bossart <nathan@postgresql.org>
[PATCH v5 1/1] Fix authorization check for role membership changes.
2026-08-07 21:50 UTC Nathan Bossart <nathan@postgresql.org>
[PATCH v5 1/1] Fix authorization check for role membership changes.
2026-08-07 21:50 UTC Nathan Bossart <nathan@postgresql.org>
[PATCH v5 1/1] Fix authorization check for role membership changes.
2026-08-07 21:50 UTC Nathan Bossart <nathan@postgresql.org>
[PATCH v5 1/1] Fix authorization check for role membership changes.
2026-08-07 21:50 UTC Nathan Bossart <nathan@postgresql.org>
[PATCH v5 1/1] Fix authorization check for role membership changes.
2026-08-07 21:50 UTC Nathan Bossart <nathan@postgresql.org>
[next (older)]
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox