public inbox for pgsql-hackers@postgresql.org
help / color / mirror / Atom feedRemoving broken support for OpenSSL without ECDH
2026-05-22 18:01 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Removing broken support for OpenSSL without ECDH
2026-05-22 18:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
[PATCH] Improving index selection for logical replication apply with replica identity full
2026-05-22 17:18 UTC Ethan Mertz <ethan.mertz@gmail.com>
Re: [PATCH] Add pg_get_policy_ddl() function to reconstruct CREATE POLICY statement
2026-01-05 14:30 UTC jian he <jian.universality@gmail.com>
` Re: [PATCH] Add pg_get_policy_ddl() function to reconstruct CREATE POLICY statement
2026-05-22 13:32 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_policy_ddl() function to reconstruct CREATE POLICY statement
2026-05-22 16:24 UTC Japin Li <japinli@hotmail.com>
[3+ messages in thread]
RFC: Allow EXPLAIN to Output Page Fault Information
2024-12-24 08:53 UTC torikoshia <torikoshia@oss.nttdata.com>
` Re: RFC: Allow EXPLAIN to Output Page Fault Information
2026-05-21 05:38 UTC vellaipandiyan sm <vellaipandiyan.sm@gmail.com>
` Re: RFC: Allow EXPLAIN to Output Page Fault Information
2026-05-22 16:07 UTC Atsushi Torikoshi <torikoshia.tech@gmail.com>
[3+ messages in thread]
Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-21 14:20 UTC Nikolay Samokhvalov <nik@postgres.ai>
` Re: Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-21 15:18 UTC Junwang Zhao <zhjwpku@gmail.com>
` Re: Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-21 17:44 UTC Kirk Wolak <wolakk@gmail.com>
` Re: Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-21 18:45 UTC Isaac Morland <isaac.morland@gmail.com>
` Re: Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-22 15:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
Avoid leaking system path from pg_available_extensions
2026-05-20 01:00 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Avoid leaking system path from pg_available_extensions
2026-05-20 01:07 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Avoid leaking system path from pg_available_extensions
2026-05-21 08:55 UTC lu feng <fnlo1995@gmail.com>
` Re: Avoid leaking system path from pg_available_extensions
2026-05-21 15:12 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: Avoid leaking system path from pg_available_extensions
2026-05-22 07:25 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: Avoid leaking system path from pg_available_extensions
2026-05-22 15:40 UTC Matheus Alcantara <matheusssilv97@gmail.com>
[6+ messages in thread]
Set notice receiver before libpq connection startup
2026-05-20 07:21 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Set notice receiver before libpq connection startup
2026-05-20 09:19 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Set notice receiver before libpq connection startup
2026-05-21 02:09 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Set notice receiver before libpq connection startup
2026-05-21 05:03 UTC vignesh C <vignesh21@gmail.com>
` Re: Set notice receiver before libpq connection startup
2026-05-21 07:26 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Set notice receiver before libpq connection startup
2026-05-22 11:33 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: Set notice receiver before libpq connection startup
2026-05-22 13:42 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Set notice receiver before libpq connection startup
2026-05-22 14:55 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Set notice receiver before libpq connection startup
2026-05-22 15:28 UTC Fujii Masao <masao.fujii@gmail.com>
[9+ messages in thread]
Prevent setting NO INHERIT on partitioned not-null constraints
2026-05-20 19:25 UTC Andreas Karlsson <andreas@proxel.se>
` Re: Prevent setting NO INHERIT on partitioned not-null constraints
2026-05-21 15:01 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: Prevent setting NO INHERIT on partitioned not-null constraints
2026-05-21 21:22 UTC Andreas Karlsson <andreas@proxel.se>
` Re: Prevent setting NO INHERIT on partitioned not-null constraints
2026-05-22 01:10 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Prevent setting NO INHERIT on partitioned not-null constraints
2026-05-22 08:10 UTC Andreas Karlsson <andreas@proxel.se>
` Re: Prevent setting NO INHERIT on partitioned not-null constraints
2026-05-22 15:02 UTC Fujii Masao <masao.fujii@gmail.com>
[6+ messages in thread]
Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-01-22 06:58 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-02-05 04:39 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-03-16 07:59 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-03-16 11:19 UTC Japin Li <japinli@hotmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-05-22 13:05 UTC Shinya Kato <shinya11.kato@gmail.com>
[5+ messages in thread]
Permission elevation by pg_amcheck operator overloading via search_path possible?
2026-05-22 12:39 UTC Pavel Borisov <pashkin.elfe@gmail.com>
Re: Adding pg_dump flag for parallel export to pipes
2026-02-20 09:08 UTC Nitin Motiani <nitinmotiani@google.com>
` Re: Adding pg_dump flag for parallel export to pipes
2026-05-21 09:56 UTC Nitin Motiani <nitinmotiani@google.com>
` Re: Adding pg_dump flag for parallel export to pipes
2026-05-22 10:34 UTC solai v <solai.cdac@gmail.com>
[3+ messages in thread]
Re: [PATCH] Preserve replication origin OIDs in pg_upgrade
2026-05-18 10:42 UTC Ajin Cherian <itsajin@gmail.com>
` Re: [PATCH] Preserve replication origin OIDs in pg_upgrade
2026-05-22 09:46 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` Re: [PATCH] Preserve replication origin OIDs in pg_upgrade
2026-05-22 10:27 UTC shveta malik <shveta.malik@gmail.com>
[3+ messages in thread]
Re: Proposal: Conflict log history table for Logical Replication
2026-01-27 03:53 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-28 04:13 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-28 12:03 UTC shveta malik <shveta.malik@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-28 12:06 UTC shveta malik <shveta.malik@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-28 20:59 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-29 05:33 UTC shveta malik <shveta.malik@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-29 06:07 UTC shveta malik <shveta.malik@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-29 11:16 UTC shveta malik <shveta.malik@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-30 06:35 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-18 09:12 UTC Nisha Moond <nisha.moond412@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-18 12:35 UTC vignesh C <vignesh21@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-19 06:31 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-19 14:00 UTC vignesh C <vignesh21@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-20 06:32 UTC shveta malik <shveta.malik@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-20 09:35 UTC vignesh C <vignesh21@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-20 10:42 UTC shveta malik <shveta.malik@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-20 10:50 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 00:02 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 01:19 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 03:59 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 04:57 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 05:51 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 06:01 UTC shveta malik <shveta.malik@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 07:08 UTC shveta malik <shveta.malik@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 07:11 UTC vignesh C <vignesh21@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 07:13 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 10:39 UTC shveta malik <shveta.malik@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-22 04:51 UTC Nisha Moond <nisha.moond412@gmail.com>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-22 10:12 UTC Nisha Moond <nisha.moond412@gmail.com>
[29+ messages in thread]
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>
[3+ messages in thread]
effective_wal_level is not decreasing after using REPACK (CONCURRENTLY)
2026-05-21 16:32 UTC Imran Zaheer <imran.zhir@gmail.com>
` Re: effective_wal_level is not decreasing after using REPACK (CONCURRENTLY)
2026-05-22 04:18 UTC shveta malik <shveta.malik@gmail.com>
` Re: effective_wal_level is not decreasing after using REPACK (CONCURRENTLY)
2026-05-22 06:10 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: effective_wal_level is not decreasing after using REPACK (CONCURRENTLY)
2026-05-22 08:57 UTC shveta malik <shveta.malik@gmail.com>
[4+ messages in thread]
[PATCH] Prevent repeated deadlock-check signals in standby buffer pin waits
2026-04-19 05:46 UTC JoongHyuk Shin <sjh910805@gmail.com>
` Re: [PATCH] Prevent repeated deadlock-check signals in standby buffer pin waits
2026-04-21 05:42 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: [PATCH] Prevent repeated deadlock-check signals in standby buffer pin waits
2026-04-21 05:55 UTC Michael Paquier <michael@paquier.xyz>
` Re: [PATCH] Prevent repeated deadlock-check signals in standby buffer pin waits
2026-04-27 11:07 UTC JoongHyuk Shin <sjh910805@gmail.com>
` Re: [PATCH] Prevent repeated deadlock-check signals in standby buffer pin waits
2026-05-18 20:32 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: [PATCH] Prevent repeated deadlock-check signals in standby buffer pin waits
2026-05-22 08:41 UTC JoongHyuk Shin <sjh910805@gmail.com>
[6+ messages in thread]
Re: Incremental View Maintenance, take 2
2023-05-31 18:47 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Incremental View Maintenance, take 2
2023-06-01 14:59 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2023-06-27 16:01 UTC jian he <jian.universality@gmail.com>
` Re: Incremental View Maintenance, take 2
2023-06-28 08:06 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2023-06-28 16:40 UTC jian he <jian.universality@gmail.com>
` Re: Incremental View Maintenance, take 2
2023-06-29 10:20 UTC jian he <jian.universality@gmail.com>
` Re: Incremental View Maintenance, take 2
2023-06-29 10:51 UTC jian he <jian.universality@gmail.com>
` Re: Incremental View Maintenance, take 2
2023-06-29 12:21 UTC jian he <jian.universality@gmail.com>
` Re: Incremental View Maintenance, take 2
2023-06-30 00:00 UTC jian he <jian.universality@gmail.com>
` Re: Incremental View Maintenance, take 2
2023-07-02 00:25 UTC jian he <jian.universality@gmail.com>
` Re: Incremental View Maintenance, take 2
2023-07-02 02:38 UTC jian he <jian.universality@gmail.com>
` Re: Incremental View Maintenance, take 2
2023-08-27 13:35 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2023-08-27 13:41 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2023-08-27 15:15 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2023-08-27 16:05 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2023-08-27 16:12 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2023-08-27 17:49 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2023-08-28 02:52 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2023-08-28 07:05 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2023-09-01 07:42 UTC jian he <jian.universality@gmail.com>
` Re: Incremental View Maintenance, take 2
2023-09-02 11:46 UTC Tatsuo Ishii <ishii@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2023-09-04 08:48 UTC jian he <jian.universality@gmail.com>
` Re: Incremental View Maintenance, take 2
2024-01-22 02:51 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Incremental View Maintenance, take 2
2024-01-23 07:23 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2024-03-04 02:53 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2024-03-04 02:53 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2024-03-04 02:58 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2024-03-29 14:47 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2024-03-31 13:59 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2024-07-02 08:03 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2024-07-11 04:23 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2024-07-27 08:26 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Incremental View Maintenance, take 2
2024-07-29 22:32 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Incremental View Maintenance, take 2
2024-07-30 05:24 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2024-07-31 06:39 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Incremental View Maintenance, take 2
2024-08-06 14:29 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Incremental View Maintenance, take 2
2024-08-08 09:37 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Incremental View Maintenance, take 2
2024-08-08 10:03 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Incremental View Maintenance, take 2
2024-08-19 21:14 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Incremental View Maintenance, take 2
2024-08-20 06:09 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Incremental View Maintenance, take 2
2024-08-20 07:06 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Incremental View Maintenance, take 2
2025-08-29 20:04 UTC Yugo Nagata <nagata@sraoss.co.jp>
` Re: Incremental View Maintenance, take 2
2025-09-12 06:09 UTC Zhang Mingli <zmlpostgres@gmail.com>
` Re: Incremental View Maintenance, take 2
2026-05-22 08:40 UTC Yugo Nagata <nagata@sraoss.co.jp>
[44+ messages in thread]
Fix pg_get_multixact_stats() members_size calculation
2026-05-22 07:02 UTC Chao Li <li.evan.chao@gmail.com>
Inquiry Regarding Parallel DML (Write-Side) Support in Future PostgreSQL Releases
2026-05-22 06:53 UTC Samil C <samillcinar@gmail.com>
Re: Available disk space per tablespace
2026-05-22 06:15 UTC solai v <solai.cdac@gmail.com>
Re: Try a presorted outer path when referenced by an ORDER BY prefix
2026-05-22 05:51 UTC Andrei Lepikhov <lepihov@gmail.com>
Re: Support EXCEPT for TABLES IN SCHEMA publications
2026-05-19 11:14 UTC Nisha Moond <nisha.moond412@gmail.com>
` Re: Support EXCEPT for TABLES IN SCHEMA publications
2026-05-22 02:26 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Support EXCEPT for TABLES IN SCHEMA publications
2026-05-22 05:30 UTC Peter Smith <smithpb2250@gmail.com>
[3+ messages in thread]
Re: pg_createsubscriber: Fix incorrect handling of cleanup flags
2026-05-22 05:27 UTC Fujii Masao <masao.fujii@gmail.com>
Re: Improve pg_stat_statements scalability
2026-05-20 22:59 UTC Sami Imseih <samimseih@gmail.com>
` Re: Improve pg_stat_statements scalability
2026-05-22 04:38 UTC Lukas Fittl <lukas@fittl.com>
[2+ messages in thread]
Fix pg_stat_wal_receiver to show CONNECTING status
2026-05-19 05:55 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Fix pg_stat_wal_receiver to show CONNECTING status
2026-05-19 13:55 UTC Michael Paquier <michael@paquier.xyz>
` Re: Fix pg_stat_wal_receiver to show CONNECTING status
2026-05-20 01:47 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Fix pg_stat_wal_receiver to show CONNECTING status
2026-05-20 04:10 UTC Michael Paquier <michael@paquier.xyz>
` Re: Fix pg_stat_wal_receiver to show CONNECTING status
2026-05-20 07:53 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Fix pg_stat_wal_receiver to show CONNECTING status
2026-05-20 20:43 UTC Michael Paquier <michael@paquier.xyz>
` Re: Fix pg_stat_wal_receiver to show CONNECTING status
2026-05-20 23:06 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Fix pg_stat_wal_receiver to show CONNECTING status
2026-05-21 07:20 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Fix pg_stat_wal_receiver to show CONNECTING status
2026-05-21 12:08 UTC Michael Paquier <michael@paquier.xyz>
` Re: Fix pg_stat_wal_receiver to show CONNECTING status
2026-05-21 12:29 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Fix pg_stat_wal_receiver to show CONNECTING status
2026-05-22 02:06 UTC Chao Li <li.evan.chao@gmail.com>
[11+ 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