agora inbox for pgsql-hackers@postgresql.org
help / color / mirror / Atom feedHow to run test coverage on Debian 13 ?
2026-10-03 16:08 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: How to run test coverage on Debian 13 ?
2026-10-03 16:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: How to run test coverage on Debian 13 ?
2026-10-03 16:22 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: How to run test coverage on Debian 13 ?
2026-10-03 16:58 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
[4+ messages in thread]
Tepid: selective index updates for heap relations
2026-06-30 17:21 UTC Greg Burd <greg@burd.me>
` Re: Tepid: selective index updates for heap relations
2026-07-01 20:49 UTC Greg Burd <greg@burd.me>
` Re: Tepid: selective index updates for heap relations
2026-07-02 16:40 UTC Greg Burd <greg@burd.me>
` Re: Tepid: selective index updates for heap relations
2026-07-03 10:54 UTC Greg Burd <greg@burd.me>
` Re: Tepid: selective index updates for heap relations
2026-07-06 13:16 UTC Greg Burd <greg@burd.me>
` Re: Tepid: selective index updates for heap relations
2026-07-08 14:05 UTC Greg Burd <greg@burd.me>
` Re: Tepid: selective index updates for heap relations
2026-07-09 11:26 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: Tepid: selective index updates for heap relations
2026-07-09 15:41 UTC Greg Burd <greg@burd.me>
` Re: Tepid: selective index updates for heap relations
2026-07-11 17:37 UTC Greg Burd <greg@burd.me>
` Re: Tepid: selective index updates for heap relations
2026-07-11 22:04 UTC Greg Burd <greg@burd.me>
` Re: Tepid: selective index updates for heap relations
2026-07-13 16:26 UTC Greg Burd <greg@burd.me>
` Re: Tepid: selective index updates for heap relations
2026-07-13 21:06 UTC Greg Burd <greg@burd.me>
` Re: Tepid: selective index updates for heap relations
2026-07-16 10:04 UTC Greg Burd <greg@burd.me>
` Re: Tepid: selective index updates for heap relations
2026-07-17 20:12 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Tepid: selective index updates for heap relations
2026-07-20 21:34 UTC Greg Burd <greg@burd.me>
` Re: Tepid: selective index updates for heap relations
2026-07-28 03:36 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Tepid: selective index updates for heap relations
2026-09-28 01:27 UTC Greg Burd <greg@burd.me>
` Re: Tepid: selective index updates for heap relations
2026-10-03 16:52 UTC Greg Burd <greg@burd.me>
[18+ messages in thread]
Coverage with make coverage-html is broken on latest Debian using lcov v2
2026-04-21 14:36 UTC Narek Galstyan <narek.galstyan@enterprisedb.com>
` Re: Coverage with make coverage-html is broken on latest Debian using lcov v2
2026-06-15 18:22 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: Coverage with make coverage-html is broken on latest Debian using lcov v2
2026-10-03 16:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
[PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-09-01 06:18 UTC Virender Singla <virender.cse@gmail.com>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-09-14 12:10 UTC Virender Singla <virender.cse@gmail.com>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-09-14 12:16 UTC Burd, Greg <greg@burd.me>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-09-14 12:31 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-09-14 13:19 UTC Greg Burd <greg@burd.me>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-09-14 15:21 UTC Andres Freund <andres@anarazel.de>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-09-14 19:19 UTC Greg Burd <greg@burd.me>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-09-15 09:42 UTC Virender Singla <virender.cse@gmail.com>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-09-15 11:12 UTC Greg Burd <greg@burd.me>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-09-21 04:24 UTC Nikolay Samokhvalov <nik@postgres.ai>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-09-29 16:31 UTC Greg Burd <greg@burd.me>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-09-30 05:39 UTC Virender Singla <virender.cse@gmail.com>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-10-01 14:16 UTC Andres Freund <andres@anarazel.de>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-10-01 16:58 UTC Andres Freund <andres@anarazel.de>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-10-02 20:41 UTC Greg Burd <greg@burd.me>
` Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
2026-10-03 16:29 UTC Greg Burd <greg@burd.me>
[16+ messages in thread]
SSI can miss conflicts between index-only scans and heap writes
2026-09-24 18:58 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: SSI can miss conflicts between index-only scans and heap writes
2026-09-29 17:37 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: SSI can miss conflicts between index-only scans and heap writes
2026-10-03 16:27 UTC Rui Zhao <zhaorui126@gmail.com>
[3+ messages in thread]
Direct TOAST v2, faster, smaller and no migration needed
2026-09-05 12:24 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-07 03:13 UTC Michael Paquier <michael@paquier.xyz>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-07 06:51 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-07 07:45 UTC Nikita Malakhov <hukutoc@gmail.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-07 08:47 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-07 08:54 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-07 08:59 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-07 09:15 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-21 09:55 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-21 12:11 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-21 15:02 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-21 18:29 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-21 18:49 UTC Andres Freund <andres@anarazel.de>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-21 20:01 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-21 20:11 UTC Tomas Vondra <tomas@vondra.me>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-21 20:12 UTC shihao zhong <zhong950419@gmail.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-21 20:21 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-22 15:44 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-25 06:49 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-27 13:14 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-29 12:18 UTC Matthias van de Meent <boekewurm+postgres@gmail.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-30 02:56 UTC Michael Paquier <michael@paquier.xyz>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-30 09:07 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-30 09:15 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-09-30 09:29 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-10-01 12:41 UTC Hannu Krosing <hannuk@google.com>
` Re: Direct TOAST v2, faster, smaller and no migration needed
2026-10-03 16:26 UTC Hannu Krosing <hannuk@google.com>
[27+ messages in thread]
Logical Implication
2026-09-11 13:35 UTC Vik Fearing <vik@postgresfriends.org>
` Re: Logical Implication
2026-09-11 14:10 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Logical Implication
2026-09-11 14:41 UTC Thom Brown <thom@linux.com>
` Re: Logical Implication
2026-09-11 16:06 UTC Vik Fearing <vik@postgresfriends.org>
` Re: Logical Implication
2026-09-11 16:12 UTC Vik Fearing <vik@postgresfriends.org>
` Re: Logical Implication
2026-09-11 16:18 UTC Vik Fearing <vik@postgresfriends.org>
` Re: Logical Implication
2026-09-17 04:53 UTC solai v <solai.cdac@gmail.com>
` Re: Logical Implication
2026-09-17 08:39 UTC Vik Fearing <vik@postgresfriends.org>
` Re: Logical Implication
2026-09-24 14:33 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Logical Implication
2026-09-29 15:20 UTC Vik Fearing <vik@postgresfriends.org>
` Re: Logical Implication
2026-09-29 16:30 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: Logical Implication
2026-09-29 16:40 UTC Isaac Morland <isaac.morland@gmail.com>
` Re: Logical Implication
2026-09-29 20:23 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Logical Implication
2026-09-29 21:51 UTC Vik Fearing <vik@postgresfriends.org>
` Re: Logical Implication
2026-09-29 22:27 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Logical Implication
2026-09-30 15:09 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Logical Implication
2026-10-03 16:18 UTC Vik Fearing <vik@postgresfriends.org>
[17+ messages in thread]
BUG #19686: Rolling back SET TABLESPACE
2026-09-16 22:06 UTC Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-09-27 18:56 UTC Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-09-27 19:09 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-09-29 08:37 UTC Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-09-29 11:45 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-09-29 19:10 UTC Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-09-29 21:44 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-09-29 22:23 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-09-29 23:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-09-30 00:08 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-09-30 07:23 UTC Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-09-30 13:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-09-30 14:16 UTC Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-10-01 08:20 UTC Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-10-02 00:57 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-10-02 03:27 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-10-02 08:35 UTC Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-10-02 14:36 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-10-02 17:06 UTC Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-10-02 17:18 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-10-02 18:30 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-10-02 18:52 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-10-02 18:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-10-02 19:34 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-10-03 04:26 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE
2026-10-03 14:39 UTC Manu <manuelreyesbravo@gmail.com>
[26+ messages in thread]
Add ASCII fast path to Unicode normalization functions
2026-09-14 14:50 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Add ASCII fast path to Unicode normalization functions
2026-09-14 15:01 UTC David E. Wheeler <david@justatheory.com>
` Re: Add ASCII fast path to Unicode normalization functions
2026-09-15 04:22 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Add ASCII fast path to Unicode normalization functions
2026-09-15 11:31 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Add ASCII fast path to Unicode normalization functions
2026-09-15 12:51 UTC Nazir Bilal Yavuz <byavuz81@gmail.com>
` Re: Add ASCII fast path to Unicode normalization functions
2026-09-15 13:15 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Add ASCII fast path to Unicode normalization functions
2026-09-17 22:46 UTC Tristan Partin <tristan@partin.io>
` Re: Add ASCII fast path to Unicode normalization functions
2026-09-18 14:11 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Add ASCII fast path to Unicode normalization functions
2026-09-18 14:52 UTC Tristan Partin <tristan@partin.io>
` Re: Add ASCII fast path to Unicode normalization functions
2026-10-03 14:27 UTC Andrew Dunstan <andrew@dunslane.net>
[10+ messages in thread]
gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower
2026-09-02 11:11 UTC Vaibhav Dalvi <vaibhav.dalvi@enterprisedb.com>
` Re: gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower
2026-09-02 13:00 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower
2026-09-02 13:29 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower
2026-09-03 06:26 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower
2026-09-03 07:40 UTC Alexander Nestorov <alexandernst@gmail.com>
` Re: gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower
2026-09-18 06:37 UTC Vaibhav Dalvi <vaibhav.dalvi@enterprisedb.com>
` Re: gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower
2026-10-03 14:07 UTC Andrew Dunstan <andrew@dunslane.net>
[7+ messages in thread]
REPACK (CONCURRENTLY) might keep dropped-column data
2026-09-30 06:27 UTC Radim Marek <radim@boringsql.com>
` Re: REPACK (CONCURRENTLY) might keep dropped-column data
2026-09-30 07:37 UTC Radim Marek <radim@boringsql.com>
` Re: REPACK (CONCURRENTLY) might keep dropped-column data
2026-09-30 11:48 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: REPACK (CONCURRENTLY) might keep dropped-column data
2026-09-30 14:41 UTC Antonin Houska <ah@cybertec.at>
` Re: REPACK (CONCURRENTLY) might keep dropped-column data
2026-09-30 15:38 UTC Radim Marek <radim@boringsql.com>
` Re: REPACK (CONCURRENTLY) might keep dropped-column data
2026-10-03 11:35 UTC Alvaro Herrera <alvherre@kurilemu.de>
` Re: REPACK (CONCURRENTLY) might keep dropped-column data
2026-10-03 13:48 UTC Alvaro Herrera <alvherre@kurilemu.de>
[7+ messages in thread]
postgres_fdw: transaction mode inheritance corner cases
2026-09-10 00:33 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: postgres_fdw: transaction mode inheritance corner cases
2026-09-10 09:24 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: postgres_fdw: transaction mode inheritance corner cases
2026-09-16 15:44 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: postgres_fdw: transaction mode inheritance corner cases
2026-09-16 20:08 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: postgres_fdw: transaction mode inheritance corner cases
2026-09-30 10:45 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: postgres_fdw: transaction mode inheritance corner cases
2026-09-30 18:27 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: postgres_fdw: transaction mode inheritance corner cases
2026-10-01 16:47 UTC Nikolay Samokhvalov <nik@postgres.ai>
` Re: postgres_fdw: transaction mode inheritance corner cases
2026-10-01 17:30 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: postgres_fdw: transaction mode inheritance corner cases
2026-10-01 17:32 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: postgres_fdw: transaction mode inheritance corner cases
2026-10-01 17:37 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: postgres_fdw: transaction mode inheritance corner cases
2026-10-02 15:54 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: postgres_fdw: transaction mode inheritance corner cases
2026-10-03 09:38 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: postgres_fdw: transaction mode inheritance corner cases
2026-10-03 12:04 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
[13+ messages in thread]
[PATCH] Refactor pgbench to make future improvements easier
2026-10-03 11:02 UTC Hannu Krosing <hannuk@google.com>
[PATCH v1] Fix for Bug#19724 - ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check
2026-09-28 13:29 UTC Nitin Motiani <nitinmotiani@google.com>
` Re: [PATCH v1] Fix for Bug#19724 - ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check
2026-09-28 14:31 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: [PATCH v1] Fix for Bug#19724 - ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check
2026-09-28 16:02 UTC Rahul Yadav <rahul@rhyadav.com>
` Re: [PATCH v1] Fix for Bug#19724 - ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check
2026-09-28 17:05 UTC Nitin Motiani <nitinmotiani@google.com>
` Re: [PATCH v1] Fix for Bug#19724 - ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check
2026-09-28 18:45 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: [PATCH v1] Fix for Bug#19724 - ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check
2026-09-28 20:40 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: [PATCH v1] Fix for Bug#19724 - ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check
2026-09-28 21:06 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: [PATCH v1] Fix for Bug#19724 - ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check
2026-09-28 23:02 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: [PATCH v1] Fix for Bug#19724 - ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check
2026-09-29 07:03 UTC Nitin Motiani <nitinmotiani@google.com>
` Re: [PATCH v1] Fix for Bug#19724 - ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check
2026-09-29 13:54 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: [PATCH v1] Fix for Bug#19724 - ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check
2026-10-03 10:20 UTC Nitin Motiani <nitinmotiani@google.com>
[11+ messages in thread]
Speed up lpad() and rpad() for one-byte padding strings
2026-09-23 14:10 UTC Sehrope Sarkuni <sehrope@jackdb.com>
` Re: Speed up lpad() and rpad() for one-byte padding strings
2026-09-23 14:41 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Speed up lpad() and rpad() for one-byte padding strings
2026-09-23 17:09 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Speed up lpad() and rpad() for one-byte padding strings
2026-09-23 17:16 UTC Sehrope Sarkuni <sehrope@jackdb.com>
` Re: Speed up lpad() and rpad() for one-byte padding strings
2026-09-23 17:19 UTC Sehrope Sarkuni <sehrope@jackdb.com>
` Re: Speed up lpad() and rpad() for one-byte padding strings
2026-09-23 22:51 UTC Sehrope Sarkuni <sehrope@jackdb.com>
` Re: Speed up lpad() and rpad() for one-byte padding strings
2026-09-24 05:21 UTC John Naylor <johncnaylorls@gmail.com>
` Re: Speed up lpad() and rpad() for one-byte padding strings
2026-09-24 11:03 UTC Sehrope Sarkuni <sehrope@jackdb.com>
` Re: Speed up lpad() and rpad() for one-byte padding strings
2026-09-24 11:20 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: Speed up lpad() and rpad() for one-byte padding strings
2026-09-24 23:54 UTC Sehrope Sarkuni <sehrope@jackdb.com>
` Re: Speed up lpad() and rpad() for one-byte padding strings
2026-09-25 01:24 UTC Manu <manuelreyesbravo@gmail.com>
` Re: Speed up lpad() and rpad() for one-byte padding strings
2026-10-03 05:27 UTC shihao zhong <zhong950419@gmail.com>
[12+ messages in thread]
[Patch]The Case For WAL-Logging pg_upgrade
2026-07-31 13:13 UTC Bohyun Lee <bohyun.lee@databricks.com>
` Re: [Patch]The Case For WAL-Logging pg_upgrade
2026-08-01 00:31 UTC John Naylor <johncnaylorls@gmail.com>
` Re: [Patch]The Case For WAL-Logging pg_upgrade
2026-08-03 09:01 UTC Bohyun Lee <bohyun.lee@databricks.com>
` Re: [Patch]The Case For WAL-Logging pg_upgrade
2026-08-05 05:15 UTC John Naylor <johncnaylorls@gmail.com>
` Re: [Patch]The Case For WAL-Logging pg_upgrade
2026-08-05 14:35 UTC Bohyun Lee <bohyun.lee@databricks.com>
` Re: [Patch]The Case For WAL-Logging pg_upgrade
2026-08-05 22:17 UTC John Naylor <johncnaylorls@gmail.com>
` Re: [Patch]The Case For WAL-Logging pg_upgrade
2026-08-06 07:39 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: [Patch]The Case For WAL-Logging pg_upgrade
2026-08-06 07:43 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: [Patch]The Case For WAL-Logging pg_upgrade
2026-08-08 06:10 UTC John Naylor <johncnaylorls@gmail.com>
` Re: [Patch]The Case For WAL-Logging pg_upgrade
2026-08-08 06:11 UTC John Naylor <johncnaylorls@gmail.com>
` Re: [Patch]The Case For WAL-Logging pg_upgrade
2026-08-12 12:49 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: [Patch]The Case For WAL-Logging pg_upgrade
2026-08-12 14:26 UTC Marco Nenciarini <marco.nenciarini@enterprisedb.com>
` Re: [Patch]The Case For WAL-Logging pg_upgrade
2026-09-08 12:59 UTC Marco Nenciarini <marco.nenciarini@enterprisedb.com>
` Re: [Patch]The Case For WAL-Logging pg_upgrade
2026-10-01 17:27 UTC Bohyun Lee <bohyun.lee@databricks.com>
` Re: [Patch]The Case For WAL-Logging pg_upgrade
2026-10-03 05:23 UTC John Naylor <johncnaylorls@gmail.com>
[15+ messages in thread]
[PATCH v1] Report relation extension blockers within parallel lock groups in pg_blocking_pids()
2026-08-29 04:24 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` [PATCH v1] Report relation extension blockers within parallel lock groups in pg_blocking_pids()
2026-08-29 04:24 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Report relation extension blockers within parallel lock groups
2026-08-31 02:39 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: Report relation extension blockers within parallel lock groups
2026-08-31 09:22 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Report relation extension blockers within parallel lock groups
2026-08-31 10:38 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: Report relation extension blockers within parallel lock groups
2026-08-31 11:28 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Report relation extension blockers within parallel lock groups
2026-09-04 05:45 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Report relation extension blockers within parallel lock groups
2026-09-22 05:04 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: Report relation extension blockers within parallel lock groups
2026-09-27 17:22 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Report relation extension blockers within parallel lock groups
2026-10-02 16:26 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Report relation extension blockers within parallel lock groups
2026-10-03 04:47 UTC shihao zhong <zhong950419@gmail.com>
[11+ messages in thread]
[PATCH v9 07/10] bufmgr: Implement buffer content locks independently of lwlocks
2025-11-19 21:37 UTC Andres Freund <andres@anarazel.de>
` [PATCH v7 12/15] bufmgr: Implement buffer content locks independently of lwlocks
2025-11-19 21:37 UTC Andres Freund <andres@anarazel.de>
` [PATCH v8 07/10] bufmgr: Implement buffer content locks independently of lwlocks
2025-11-19 21:37 UTC Andres Freund <andres@anarazel.de>
` [PATCH v6 08/14] bufmgr: Implement buffer content locks independently of lwlocks
2025-11-19 21:37 UTC Andres Freund <andres@anarazel.de>
` [PATCH v11 2/7] bufmgr: Implement buffer content locks independently of lwlocks
2026-01-14 01:10 UTC Andres Freund <andres@anarazel.de>
` [PATCH] Fix pg_dump emitting OVERRIDING SYSTEM VALUE for tables with dropped identity columns
2026-04-17 23:29 UTC William Bernbaum <wbernbaum@dwdev.com>
` Re: [PATCH] Fix pg_dump emitting OVERRIDING SYSTEM VALUE for tables with dropped identity columns
2026-05-01 07:28 UTC Andreas Karlsson <andreas@proxel.se>
` Re: [PATCH] Fix pg_dump emitting OVERRIDING SYSTEM VALUE for tables with dropped identity columns
2026-05-01 07:39 UTC Andreas Karlsson <andreas@proxel.se>
` RE: [PATCH] Fix pg_dump emitting OVERRIDING SYSTEM VALUE for tables with dropped identity columns
2026-09-01 19:14 UTC William Bernbaum <wbernbaum@dwdev.com>
` Re: [PATCH] Fix pg_dump emitting OVERRIDING SYSTEM VALUE for tables with dropped identity columns
2026-09-02 01:14 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: [PATCH] Fix pg_dump emitting OVERRIDING SYSTEM VALUE for tables with dropped identity columns
2026-09-10 09:37 UTC solai v <solai.cdac@gmail.com>
` Re: [PATCH] Fix pg_dump emitting OVERRIDING SYSTEM VALUE for tables with dropped identity columns
2026-10-03 04:33 UTC shihao zhong <zhong950419@gmail.com>
[12+ messages in thread]
doc: Document Linux cgroup memory limits
2026-10-01 22:19 UTC Joao Detomini <joao.detomini@enterprisedb.com>
` Re: doc: Document Linux cgroup memory limits
2026-10-03 03:08 UTC Manu <manuelreyesbravo@gmail.com>
[2+ messages in thread]
Revert RI fast-path batching from REL_19_STABLE
2026-09-03 13:36 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-07 13:14 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-08 05:11 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-08 08:01 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-08 09:52 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-08 13:01 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-08 17:59 UTC Robert Haas <robertmhaas@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-09 11:57 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-09 12:25 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-09 15:41 UTC Melanie Plageman <melanieplageman@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-09 19:45 UTC Robert Haas <robertmhaas@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-10 03:57 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-10 06:20 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-10 08:58 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-11 08:52 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-09-23 08:48 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-10-01 12:05 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Revert RI fast-path batching from REL_19_STABLE
2026-10-03 02:47 UTC Amit Langote <amitlangote09@gmail.com>
[18+ messages in thread]
Fix reindexdb with parallel index-level conrurrent run
2026-10-02 17:03 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Fix reindexdb with parallel index-level conrurrent run
2026-10-03 01:48 UTC Manu <manuelreyesbravo@gmail.com>
[2+ messages in thread]
Adding a stored generated column without long-lived locks
2026-03-17 10:31 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-04-07 09:09 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-04-24 09:10 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-05-14 22:46 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-05-26 15:23 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-05-27 17:43 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-05-27 17:44 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-06-15 18:38 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-06-15 20:41 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-06-30 13:44 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-07-03 06:42 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-07-07 18:16 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-07-10 00:10 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-07-10 06:51 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-08-06 12:36 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-08-24 17:29 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-08-24 20:03 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-08-25 08:46 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-08-25 16:13 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-08-26 05:20 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-08-28 05:50 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-08-28 13:36 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-08-28 16:07 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-08-29 06:14 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-08-31 18:41 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-09-01 04:58 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-09-01 09:02 UTC solai v <solai.cdac@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-09-01 15:41 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-09-16 17:02 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-09-21 21:48 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-09-22 13:02 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-09-22 13:37 UTC Matthias van de Meent <boekewurm+postgres@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-09-22 15:17 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: Adding a stored generated column without long-lived locks
2026-09-23 10:07 UTC Matthias van de Meent <boekewurm+postgres@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-09-23 10:26 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-09-23 22:19 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-09-24 10:47 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-10-01 23:30 UTC Alberto Piai <alberto.piai@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-10-02 07:30 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Adding a stored generated column without long-lived locks
2026-10-02 16:58 UTC Matthias van de Meent <boekewurm+postgres@gmail.com>
` Re: Adding a stored generated column without long-lived locks
2026-10-03 01:25 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[41+ messages in thread]
injection_points: canceled or terminated waiters leak their wait slots
2026-07-21 08:28 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-07-22 01:29 UTC Michael Paquier <michael@paquier.xyz>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-07-22 06:07 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-07-22 06:28 UTC Michael Paquier <michael@paquier.xyz>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-07-23 05:40 UTC Michael Paquier <michael@paquier.xyz>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-08-23 09:13 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-09-23 16:42 UTC Nikolay Samokhvalov <nik@postgres.ai>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-09-28 22:12 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-09-28 22:57 UTC Michael Paquier <michael@paquier.xyz>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-09-29 00:38 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-09-29 11:24 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-09-29 23:46 UTC Michael Paquier <michael@paquier.xyz>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-09-30 12:31 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-09-30 16:14 UTC Kacper Kuras <kacperkuras@hotmail.com>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-09-30 18:00 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-09-30 22:55 UTC Michael Paquier <michael@paquier.xyz>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-09-30 23:05 UTC Michael Paquier <michael@paquier.xyz>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-10-02 21:44 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: injection_points: canceled or terminated waiters leak their wait slots
2026-10-02 23:48 UTC Michael Paquier <michael@paquier.xyz>
[19+ messages in thread]
Allow table AMs to define their own reloptions
2025-03-02 08:56 UTC Julien Tachoires <julien@tachoires.me>
` Re: Allow table AMs to define their own reloptions
2025-03-02 13:23 UTC Julien Tachoires <julien@tachoires.me>
` Re: Allow table AMs to define their own reloptions
2025-03-02 15:20 UTC Yura Sokolov <y.sokolov@postgrespro.ru>
` Re: Allow table AMs to define their own reloptions
2025-03-04 06:16 UTC Julien Tachoires <julien@tachoires.me>
` Re: Allow table AMs to define their own reloptions
2025-03-04 09:19 UTC Yura Sokolov <y.sokolov@postgrespro.ru>
` Re: Allow table AMs to define their own reloptions
2025-03-29 07:46 UTC Julien Tachoires <julien@tachoires.me>
` Re: Allow table AMs to define their own reloptions
2025-05-26 11:06 UTC Julien Tachoires <julien@tachoires.me>
` Re: Allow table AMs to define their own reloptions
2026-06-03 23:02 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Allow table AMs to define their own reloptions
2026-07-16 13:37 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: Allow table AMs to define their own reloptions
2026-07-16 14:32 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Allow table AMs to define their own reloptions
2026-07-20 06:52 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: Allow table AMs to define their own reloptions
2026-08-13 11:11 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Allow table AMs to define their own reloptions
2026-08-14 21:46 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Allow table AMs to define their own reloptions
2026-08-17 09:40 UTC Junwang Zhao <zhjwpku@gmail.com>
` Re: Allow table AMs to define their own reloptions
2026-08-17 09:45 UTC Junwang Zhao <zhjwpku@gmail.com>
` Re: Allow table AMs to define their own reloptions
2026-08-21 19:09 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Allow table AMs to define their own reloptions
2026-08-26 15:53 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Allow table AMs to define their own reloptions
2026-08-28 19:43 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Allow table AMs to define their own reloptions
2026-08-31 12:27 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Allow table AMs to define their own reloptions
2026-09-07 11:15 UTC Ajit Awekar <ajitpostgres@gmail.com>
` Re: Allow table AMs to define their own reloptions
2026-09-07 12:41 UTC Aleksander Alekseev <aleksander@tigerdata.com>
` Re: Allow table AMs to define their own reloptions
2026-09-08 10:03 UTC Ajit Awekar <ajitpostgres@gmail.com>
` Re: Allow table AMs to define their own reloptions
2026-09-08 12:34 UTC Ajit Awekar <ajitpostgres@gmail.com>
` Re: Allow table AMs to define their own reloptions
2026-09-10 17:50 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Allow table AMs to define their own reloptions
2026-09-28 13:23 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Allow table AMs to define their own reloptions
2026-09-30 08:35 UTC Ajit Awekar <ajitpostgres@gmail.com>
` Re: Allow table AMs to define their own reloptions
2026-09-30 13:45 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Allow table AMs to define their own reloptions
2026-09-30 21:22 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Allow table AMs to define their own reloptions
2026-10-01 12:59 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Allow table AMs to define their own reloptions
2026-10-01 14:57 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: Allow table AMs to define their own reloptions
2026-10-02 21:48 UTC Andrew Dunstan <andrew@dunslane.net>
[31+ messages in thread]
Costing for parallel scans with few/single row produced in the outer side
2026-09-28 22:06 UTC Matthias van de Meent <boekewurm@gmail.com>
` Re: Costing for parallel scans with few/single row produced in the outer side
2026-09-29 14:50 UTC Robert Haas <robertmhaas@gmail.com>
` Re: Costing for parallel scans with few/single row produced in the outer side
2026-09-29 21:05 UTC Matthias van de Meent <boekewurm@gmail.com>
` Re: Costing for parallel scans with few/single row produced in the outer side
2026-09-30 05:36 UTC Haibo Yan <tristan.yim@gmail.com>
` Re: Costing for parallel scans with few/single row produced in the outer side
2026-10-02 21:10 UTC Matthias van de Meent <boekewurm@gmail.com>
[5+ messages in thread]
[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