public inbox for [email protected]
help / color / mirror / Atom feed Re: quoteOneName() inconsistency with quote_all_identifiers — replacement API proposed
2026-04-13 08:16 UTC David Rowley <[email protected]>
` Re: quoteOneName() inconsistency with quote_all_identifiers — replacement API proposed
2026-04-13 09:28 UTC Chao Li <[email protected]>
[2+ messages in thread]
Unicode update and some tooling improvements
2026-02-26 20:36 UTC Peter Eisentraut <[email protected]>
` Re: Unicode update and some tooling improvements
2026-03-13 10:11 UTC Alexander Borisov <[email protected]>
` Re: Unicode update and some tooling improvements
2026-03-18 14:20 UTC Andres Freund <[email protected]>
` Re: Unicode update and some tooling improvements
2026-03-20 07:50 UTC Peter Eisentraut <[email protected]>
` Re: Unicode update and some tooling improvements
2026-04-13 09:21 UTC Peter Eisentraut <[email protected]>
[5+ messages in thread]
Re: Proposal for enabling auto-vectorization for checksum calculations
2026-01-11 23:19 UTC John Naylor <[email protected]>
` Re: Proposal for enabling auto-vectorization for checksum calculations
2026-01-13 01:58 UTC Andrew Kim <[email protected]>
` Re: Proposal for enabling auto-vectorization for checksum calculations
2026-01-13 05:07 UTC John Naylor <[email protected]>
` Re: Proposal for enabling auto-vectorization for checksum calculations
2026-01-15 08:03 UTC Oleg Tselebrovskiy <[email protected]>
` Re: Proposal for enabling auto-vectorization for checksum calculations
2026-01-15 10:35 UTC John Naylor <[email protected]>
` Re: Proposal for enabling auto-vectorization for checksum calculations
2026-01-21 11:13 UTC John Naylor <[email protected]>
` Re: Proposal for enabling auto-vectorization for checksum calculations
2026-02-09 08:42 UTC Andrew Kim <[email protected]>
` Re: Proposal for enabling auto-vectorization for checksum calculations
2026-03-16 08:00 UTC Andrew Kim <[email protected]>
` Re: Proposal for enabling auto-vectorization for checksum calculations
2026-03-17 02:23 UTC John Naylor <[email protected]>
` Re: Proposal for enabling auto-vectorization for checksum calculations
2026-03-17 02:25 UTC John Naylor <[email protected]>
` Re: Proposal for enabling auto-vectorization for checksum calculations
2026-03-30 12:01 UTC John Naylor <[email protected]>
` Re: Proposal for enabling auto-vectorization for checksum calculations
2026-03-30 15:00 UTC Ants Aasma <[email protected]>
` Re: Proposal for enabling auto-vectorization for checksum calculations
2026-03-31 04:09 UTC John Naylor <[email protected]>
` Re: Proposal for enabling auto-vectorization for checksum calculations
2026-04-04 13:25 UTC John Naylor <[email protected]>
` Re: Proposal for enabling auto-vectorization for checksum calculations
2026-04-13 08:32 UTC Andrew Kim <[email protected]>
[15+ messages in thread]
RE: Warn when creating or enabling a subscription with max_logical_replication_workers = 0
2026-02-05 08:12 UTC Zhijie Hou (Fujitsu) <[email protected]>
` Re: Warn when creating or enabling a subscription with max_logical_replication_workers = 0
2026-02-05 22:58 UTC Peter Smith <[email protected]>
` Re: Warn when creating or enabling a subscription with max_logical_replication_workers = 0
2026-02-06 04:37 UTC Yugo Nagata <[email protected]>
` Re: Warn when creating or enabling a subscription with max_logical_replication_workers = 0
2026-02-06 07:28 UTC Peter Smith <[email protected]>
` Re: Warn when creating or enabling a subscription with max_logical_replication_workers = 0
2026-04-13 07:04 UTC Yugo Nagata <[email protected]>
[5+ messages in thread]
Re: Extension - multilingual_fuzzy_match : Multilingual phonetic matching extension for PostgreSQL
2026-04-13 06:57 UTC lakshmi <[email protected]>
RE: subscriptionCheck failures on nightjar
2026-04-13 05:01 UTC Hayato Kuroda (Fujitsu) <[email protected]>
Re: quoteOneName() inconsistency with quote_all_identifiers — replacement API proposed
2026-04-13 02:53 UTC Chao Li <[email protected]>
Small and unlikely overflow hazard in bms_next_member()
2026-04-02 04:09 UTC David Rowley <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-02 04:22 UTC Tom Lane <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-02 06:38 UTC Chao Li <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-02 07:54 UTC jie wang <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-02 22:12 UTC David Rowley <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-02 22:20 UTC David Rowley <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-03 02:08 UTC David Rowley <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-03 03:24 UTC Chao Li <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-03 11:42 UTC David Rowley <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-03 13:28 UTC Chao Li <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-04 03:30 UTC David Rowley <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-06 02:00 UTC Chao Li <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-12 12:33 UTC David Rowley <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-12 13:17 UTC David Rowley <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-12 23:41 UTC David Rowley <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-13 00:23 UTC Chao Li <[email protected]>
` Re: Small and unlikely overflow hazard in bms_next_member()
2026-04-13 02:43 UTC David Rowley <[email protected]>
[17+ messages in thread]
RE: [Proposal] Expose internal MultiXact member count function for efficient monitoring
2026-04-13 01:28 UTC Shinoda, Noriyoshi (PSD Japan FSI) <[email protected]>
Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-02-24 19:48 UTC Mihail Nikalayeu <[email protected]>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-03-09 00:09 UTC Mihail Nikalayeu <[email protected]>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-03-23 22:08 UTC Mihail Nikalayeu <[email protected]>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-03-28 19:17 UTC Mihail Nikalayeu <[email protected]>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-03-31 22:11 UTC Mihail Nikalayeu <[email protected]>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-04-06 18:21 UTC Mihail Nikalayeu <[email protected]>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-04-07 01:42 UTC Josh Kupershmidt <[email protected]>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-04-07 23:19 UTC Mihail Nikalayeu <[email protected]>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-04-11 16:56 UTC Mihail Nikalayeu <[email protected]>
` Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
2026-04-13 01:05 UTC Josh Kupershmidt <[email protected]>
[10+ messages in thread]
Fix pgstat_database.c to honor passed database OIDs
2026-04-10 05:53 UTC Chao Li <[email protected]>
` Re: Fix pgstat_database.c to honor passed database OIDs
2026-04-10 06:12 UTC Michael Paquier <[email protected]>
` Re: Fix pgstat_database.c to honor passed database OIDs
2026-04-10 07:56 UTC Michael Paquier <[email protected]>
` Re: Fix pgstat_database.c to honor passed database OIDs
2026-04-10 08:44 UTC Chao Li <[email protected]>
` Re: Fix pgstat_database.c to honor passed database OIDs
2026-04-10 13:01 UTC Dapeng Wang <[email protected]>
` Re: Fix pgstat_database.c to honor passed database OIDs
2026-04-13 00:16 UTC Michael Paquier <[email protected]>
` Re: Fix pgstat_database.c to honor passed database OIDs
2026-04-13 00:43 UTC Chao Li <[email protected]>
[7+ messages in thread]
Non-compliant SASLprep implementation for ASCII characters
2026-02-27 03:05 UTC Michael Paquier <[email protected]>
` Re: Non-compliant SASLprep implementation for ASCII characters
2026-03-02 07:02 UTC Michael Paquier <[email protected]>
` Re: Non-compliant SASLprep implementation for ASCII characters
2026-03-18 11:34 UTC John Naylor <[email protected]>
` Re: Non-compliant SASLprep implementation for ASCII characters
2026-03-19 04:25 UTC Michael Paquier <[email protected]>
` Re: Non-compliant SASLprep implementation for ASCII characters
2026-03-23 23:33 UTC Michael Paquier <[email protected]>
` Re: Non-compliant SASLprep implementation for ASCII characters
2026-04-12 06:00 UTC Alexander Lakhin <[email protected]>
` Re: Non-compliant SASLprep implementation for ASCII characters
2026-04-12 11:47 UTC Michael Paquier <[email protected]>
` Re: Non-compliant SASLprep implementation for ASCII characters
2026-04-12 13:00 UTC Alexander Lakhin <[email protected]>
` Re: Non-compliant SASLprep implementation for ASCII characters
2026-04-13 00:12 UTC Michael Paquier <[email protected]>
[9+ messages in thread]
Use stack allocated StringInfoDatas, where possible (round 2)
2026-04-12 10:49 UTC Bertrand Drouvot <[email protected]>
` Re: Use stack allocated StringInfoDatas, where possible (round 2)
2026-04-12 13:34 UTC David Rowley <[email protected]>
` Re: Use stack allocated StringInfoDatas, where possible (round 2)
2026-04-12 22:45 UTC David Rowley <[email protected]>
[3+ messages in thread]
Re: Change default of jit to off
2026-02-03 10:29 UTC Christoph Berg <[email protected]>
` Re: Change default of jit to off
2026-02-03 15:46 UTC Adrien Nayrat <[email protected]>
` Re: Change default of jit to off
2026-02-03 17:03 UTC Greg Sabino Mullane <[email protected]>
` Re: Change default of jit to off
2026-02-03 17:13 UTC Andres Freund <[email protected]>
` Re: Change default of jit to off
2026-02-13 14:57 UTC Jelte Fennema-Nio <[email protected]>
` Re: Change default of jit to off
2026-03-23 06:33 UTC Pierre Ducroquet <[email protected]>
` Re: Change default of jit to off
2026-03-24 14:32 UTC Jelte Fennema-Nio <[email protected]>
` Re: Change default of jit to off
2026-03-24 21:56 UTC Andres Freund <[email protected]>
` Re: Change default of jit to off
2026-03-25 22:10 UTC Tomas Vondra <[email protected]>
` Re: Change default of jit to off
2026-04-02 11:51 UTC Tomas Vondra <[email protected]>
` Re: Change default of jit to off
2026-04-02 12:50 UTC Thomas Munro <[email protected]>
` Re: Change default of jit to off
2026-04-02 13:10 UTC Andrew Dunstan <[email protected]>
` Re: Change default of jit to off
2026-04-02 13:46 UTC Greg Sabino Mullane <[email protected]>
` Re: Change default of jit to off
2026-04-02 14:01 UTC Andrew Dunstan <[email protected]>
` Re: Change default of jit to off
2026-04-02 19:46 UTC Tomas Vondra <[email protected]>
` Re: Change default of jit to off
2026-04-12 22:27 UTC Tomas Vondra <[email protected]>
[16+ messages in thread]
pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-01 06:44 UTC Fujii Masao <[email protected]>
` Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-02 19:56 UTC Robert Haas <[email protected]>
` Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-03 00:45 UTC Fujii Masao <[email protected]>
` Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-06 14:55 UTC Robert Haas <[email protected]>
` Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-06 15:57 UTC Fujii Masao <[email protected]>
` Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-06 16:15 UTC Robert Haas <[email protected]>
` Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-07 03:04 UTC Fujii Masao <[email protected]>
` Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-07 03:18 UTC Amit Kapila <[email protected]>
` Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-07 03:32 UTC Amit Kapila <[email protected]>
` Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-07 03:51 UTC Fujii Masao <[email protected]>
` Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-07 03:54 UTC Fujii Masao <[email protected]>
` Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-07 06:08 UTC Fujii Masao <[email protected]>
` Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-10 09:54 UTC Amit Kapila <[email protected]>
` Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-10 14:01 UTC Fujii Masao <[email protected]>
` Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
2026-04-12 17:55 UTC Tom Lane <[email protected]>
[15+ messages in thread]
[PATCH v1] Use stack allocated StringInfoDatas, where possible
2026-04-12 10:09 UTC Bertrand Drouvot <[email protected]>
Add missing CHECK_FOR_INTERRUPTS in autovacuum catalog scan loops
2026-04-10 08:38 UTC Lakshmi N <[email protected]>
` Re: Add missing CHECK_FOR_INTERRUPTS in autovacuum catalog scan loops
2026-04-10 11:57 UTC Dapeng Wang <[email protected]>
` Re: Add missing CHECK_FOR_INTERRUPTS in autovacuum catalog scan loops
2026-04-11 05:02 UTC Lakshmi N <[email protected]>
` Re: Add missing CHECK_FOR_INTERRUPTS in autovacuum catalog scan loops
2026-04-11 12:19 UTC Dapeng Wang <[email protected]>
` Re: Add missing CHECK_FOR_INTERRUPTS in autovacuum catalog scan loops
2026-04-11 20:10 UTC Sami Imseih <[email protected]>
[5+ messages in thread]
pg17: XX000: no relation entry for relid 0
2026-04-10 10:54 UTC Justin Pryzby <[email protected]>
` Re: pg17: XX000: no relation entry for relid 0
2026-04-10 12:49 UTC Tender Wang <[email protected]>
` Re: pg17: XX000: no relation entry for relid 0
2026-04-10 14:38 UTC Richard Guo <[email protected]>
` Re: pg17: XX000: no relation entry for relid 0
2026-04-10 20:34 UTC Michael Paquier <[email protected]>
` Re: pg17: XX000: no relation entry for relid 0
2026-04-11 01:31 UTC Tender Wang <[email protected]>
` Re: pg17: XX000: no relation entry for relid 0
2026-04-11 07:57 UTC Richard Guo <[email protected]>
[6+ messages in thread]
[PATCH v1 1/2] contrib/io_limit: Simulation of slow storage.
2026-04-11 05:31 UTC Thomas Munro <[email protected]>
Possible mismatch between behaviour and documentation in CREATE FUNCTION
2026-04-11 03:40 UTC Isaac Morland <[email protected]>
` Re: Possible mismatch between behaviour and documentation in CREATE FUNCTION
2026-04-11 03:53 UTC David G. Johnston <[email protected]>
[2+ messages in thread]
[PATCH] Use cached hash to skip unnecessary key comparisons in dshash
2026-04-10 16:09 UTC CharSyam <[email protected]>
` Re: [PATCH] Use cached hash to skip unnecessary key comparisons in dshash
2026-04-10 18:07 UTC Nathan Bossart <[email protected]>
` Re: [PATCH] Use cached hash to skip unnecessary key comparisons in dshash
2026-04-10 18:10 UTC Nathan Bossart <[email protected]>
` Re: [PATCH] Use cached hash to skip unnecessary key comparisons in dshash
2026-04-11 01:17 UTC CharSyam <[email protected]>
[4+ messages in thread]
Re: pg_plan_advice: rtekind uninitialized compilation waning
2026-04-10 15:59 UTC Robert Haas <[email protected]>
Re: Fix slotsync worker busy loop causing repeated log messages
2026-02-28 05:03 UTC Amit Kapila <[email protected]>
` RE: Fix slotsync worker busy loop causing repeated log messages
2026-03-03 07:42 UTC Zhijie Hou (Fujitsu) <[email protected]>
` Re: Fix slotsync worker busy loop causing repeated log messages
2026-03-03 10:25 UTC Amit Kapila <[email protected]>
` RE: Fix slotsync worker busy loop causing repeated log messages
2026-03-03 12:24 UTC Zhijie Hou (Fujitsu) <[email protected]>
` RE: Fix slotsync worker busy loop causing repeated log messages
2026-03-04 02:59 UTC =?utf-8?B?Y2NhNTUwNw==?= <[email protected]>
` RE: Fix slotsync worker busy loop causing repeated log messages
2026-03-06 11:04 UTC Zhijie Hou (Fujitsu) <[email protected]>
` Re: Fix slotsync worker busy loop causing repeated log messages
2026-03-19 13:38 UTC Fujii Masao <[email protected]>
` Re: Fix slotsync worker busy loop causing repeated log messages
2026-03-21 17:46 UTC Amit Kapila <[email protected]>
` RE: Fix slotsync worker busy loop causing repeated log messages
2026-04-10 02:58 UTC Zhijie Hou (Fujitsu) <[email protected]>
` Re: Fix slotsync worker busy loop causing repeated log messages
2026-04-10 04:17 UTC Amit Kapila <[email protected]>
` Re: Fix slotsync worker busy loop causing repeated log messages
2026-04-10 06:01 UTC shveta malik <[email protected]>
` Re: Fix slotsync worker busy loop causing repeated log messages
2026-04-10 09:52 UTC Amit Kapila <[email protected]>
` RE: Fix slotsync worker busy loop causing repeated log messages
2026-04-10 10:28 UTC Zhijie Hou (Fujitsu) <[email protected]>
[13+ messages in thread]
[PATCH] Do not push the active snapshot for copy_table_data before it's needed.
2026-04-10 10:17 UTC Antonin Houska <[email protected]>
[PATCH] Do not push the active snapshot for copy_table_data before it's needed.
2026-04-10 10:17 UTC Antonin Houska <[email protected]>
[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