public inbox for [email protected]
help / color / mirror / Atom feedFix bug of CHECK constraint enforceability recursion
2026-05-26 03:51 UTC Chao Li <[email protected]>
` Re: Fix bug of CHECK constraint enforceability recursion
2026-05-26 05:48 UTC Chao Li <[email protected]>
` Re: Fix bug of CHECK constraint enforceability recursion
2026-05-26 06:05 UTC jian he <[email protected]>
` Re: Fix bug of CHECK constraint enforceability recursion
2026-05-26 06:27 UTC Chao Li <[email protected]>
` Re: Fix bug of CHECK constraint enforceability recursion
2026-05-26 07:32 UTC Álvaro Herrera <[email protected]>
` Re: Fix bug of CHECK constraint enforceability recursion
2026-05-26 07:44 UTC Chao Li <[email protected]>
` Re: Fix bug of CHECK constraint enforceability recursion
2026-05-26 07:46 UTC Chao Li <[email protected]>
[7+ messages in thread]
libpq maligning postgres stability
2025-03-27 15:19 UTC Andres Freund <[email protected]>
` Re: libpq maligning postgres stability
2025-03-27 15:48 UTC Robert Haas <[email protected]>
` Re: libpq maligning postgres stability
2025-03-27 16:03 UTC Christoph Berg <[email protected]>
` Re: libpq maligning postgres stability
2025-04-07 22:37 UTC Bruce Momjian <[email protected]>
` Re: libpq maligning postgres stability
2026-05-26 07:22 UTC Jelte Fennema-Nio <[email protected]>
[5+ messages in thread]
Avoid leaking system path from pg_available_extensions
2026-05-20 01:00 UTC Chao Li <[email protected]>
` Re: Avoid leaking system path from pg_available_extensions
2026-05-20 01:07 UTC Chao Li <[email protected]>
` Re: Avoid leaking system path from pg_available_extensions
2026-05-21 08:55 UTC lu feng <[email protected]>
` Re: Avoid leaking system path from pg_available_extensions
2026-05-21 15:12 UTC Matheus Alcantara <[email protected]>
` Re: Avoid leaking system path from pg_available_extensions
2026-05-22 07:25 UTC Jim Jones <[email protected]>
` Re: Avoid leaking system path from pg_available_extensions
2026-05-22 15:40 UTC Matheus Alcantara <[email protected]>
` Re: Avoid leaking system path from pg_available_extensions
2026-05-26 07:14 UTC Chao Li <[email protected]>
[7+ messages in thread]
Re:[PATCH] Little refactoring of portalcmds.c
2026-05-26 07:05 UTC =?utf-8?B?Wml6aHVhbiBMaXU=?= <[email protected]>
Re: pg_rewind does not rewind diverging timelines
2026-05-21 22:09 UTC surya poondla <[email protected]>
` Re: pg_rewind does not rewind diverging timelines
2026-05-24 18:30 UTC Mats Kindahl <[email protected]>
` Re: pg_rewind does not rewind diverging timelines
2026-05-25 05:20 UTC Japin Li <[email protected]>
` Re: pg_rewind does not rewind diverging timelines
2026-05-25 18:59 UTC Mats Kindahl <[email protected]>
` Re: pg_rewind does not rewind diverging timelines
2026-05-26 06:56 UTC Japin Li <[email protected]>
[5+ messages in thread]
Fix bug of UPDATE/DELETE FOR PORTION OF with inheritance tables
2026-05-07 03:40 UTC Chao Li <[email protected]>
` Re: Fix bug of UPDATE/DELETE FOR PORTION OF with inheritance tables
2026-05-09 05:47 UTC Chao Li <[email protected]>
` Re: Fix bug of UPDATE/DELETE FOR PORTION OF with inheritance tables
2026-05-25 23:01 UTC Paul A Jungwirth <[email protected]>
` Re: Fix bug of UPDATE/DELETE FOR PORTION OF with inheritance tables
2026-05-26 06:55 UTC Chao Li <[email protected]>
[4+ messages in thread]
POC: PLpgSQL FOREACH IN JSON ARRAY
2026-02-28 07:10 UTC Pavel Stehule <[email protected]>
` Re: POC: PLpgSQL FOREACH IN JSON ARRAY
2026-03-11 20:57 UTC Peter Eisentraut <[email protected]>
` Re: POC: PLpgSQL FOREACH IN JSON ARRAY
2026-03-12 07:00 UTC Pavel Stehule <[email protected]>
` Re: POC: PLpgSQL FOREACH IN JSON ARRAY
2026-03-17 06:58 UTC Pavel Stehule <[email protected]>
` Re: POC: PLpgSQL FOREACH IN JSON ARRAY
2026-03-21 18:40 UTC Pavel Stehule <[email protected]>
` Re: POC: PLpgSQL FOREACH IN JSON ARRAY
2026-05-26 06:51 UTC Pavel Stehule <[email protected]>
[6+ messages in thread]
Re: Proposal: Conflict log history table for Logical Replication
2026-01-27 03:53 UTC Dilip Kumar <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-28 04:13 UTC Peter Smith <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-28 12:03 UTC shveta malik <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-28 12:06 UTC shveta malik <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-28 20:59 UTC Peter Smith <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-29 05:33 UTC shveta malik <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-29 06:07 UTC shveta malik <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-29 11:16 UTC shveta malik <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-01-30 06:35 UTC Dilip Kumar <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-18 09:12 UTC Nisha Moond <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-18 12:35 UTC vignesh C <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-19 06:31 UTC Peter Smith <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-19 14:00 UTC vignesh C <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-20 06:32 UTC shveta malik <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-20 09:35 UTC vignesh C <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-20 10:42 UTC shveta malik <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-20 10:50 UTC Shlok Kyal <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 00:02 UTC Peter Smith <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 01:19 UTC Peter Smith <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 03:59 UTC Peter Smith <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 04:57 UTC Peter Smith <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 05:51 UTC Peter Smith <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 06:01 UTC shveta malik <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 07:08 UTC shveta malik <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 07:11 UTC vignesh C <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 07:13 UTC Shlok Kyal <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-21 10:39 UTC shveta malik <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-22 04:51 UTC Nisha Moond <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-22 10:12 UTC Nisha Moond <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-23 06:10 UTC vignesh C <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-23 15:40 UTC Amit Kapila <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-25 01:36 UTC Peter Smith <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-25 04:18 UTC shveta malik <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-25 04:42 UTC vignesh C <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-26 05:53 UTC vignesh C <[email protected]>
` Re: Proposal: Conflict log history table for Logical Replication
2026-05-26 06:28 UTC Peter Smith <[email protected]>
[36+ messages in thread]
bugfix - fix broken output in expanded aligned format, when data are too short
2026-03-23 19:42 UTC Pavel Stehule <[email protected]>
` Re: bugfix - fix broken output in expanded aligned format, when data are too short
2026-03-24 05:46 UTC Pavel Stehule <[email protected]>
` Re: bugfix - fix broken output in expanded aligned format, when data are too short
2026-03-24 06:12 UTC Chao Li <[email protected]>
` Re: bugfix - fix broken output in expanded aligned format, when data are too short
2026-03-24 06:31 UTC Pavel Stehule <[email protected]>
` Re: bugfix - fix broken output in expanded aligned format, when data are too short
2026-03-24 07:23 UTC Pavel Stehule <[email protected]>
` Re: bugfix - fix broken output in expanded aligned format, when data are too short
2026-05-26 06:22 UTC Pavel Stehule <[email protected]>
[6+ messages in thread]
PostgreSQL and OpenSSL 4.0.0
2026-04-16 13:32 UTC Daniel Gustafsson <[email protected]>
` Re: PostgreSQL and OpenSSL 4.0.0
2026-04-17 21:50 UTC Michael Paquier <[email protected]>
` Re: PostgreSQL and OpenSSL 4.0.0
2026-05-07 13:44 UTC Daniel Gustafsson <[email protected]>
` Re: PostgreSQL and OpenSSL 4.0.0
2026-05-07 19:32 UTC Cary Huang <[email protected]>
` Re: PostgreSQL and OpenSSL 4.0.0
2026-05-07 19:39 UTC Daniel Gustafsson <[email protected]>
` Re: PostgreSQL and OpenSSL 4.0.0
2026-05-07 19:51 UTC Daniel Gustafsson <[email protected]>
` Re: PostgreSQL and OpenSSL 4.0.0
2026-05-07 22:13 UTC Michael Paquier <[email protected]>
` Re: PostgreSQL and OpenSSL 4.0.0
2026-05-07 22:22 UTC Tom Lane <[email protected]>
` Re: PostgreSQL and OpenSSL 4.0.0
2026-05-07 22:54 UTC Cary Huang <[email protected]>
` Re: PostgreSQL and OpenSSL 4.0.0
2026-05-08 07:07 UTC Daniel Gustafsson <[email protected]>
` Re: PostgreSQL and OpenSSL 4.0.0
2026-05-08 07:17 UTC Michael Paquier <[email protected]>
` Re: PostgreSQL and OpenSSL 4.0.0
2026-05-08 07:21 UTC Daniel Gustafsson <[email protected]>
` Re: PostgreSQL and OpenSSL 4.0.0
2026-05-19 21:18 UTC Daniel Gustafsson <[email protected]>
` Re: PostgreSQL and OpenSSL 4.0.0
2026-05-26 06:02 UTC Michael Paquier <[email protected]>
[14+ messages in thread]
Re: Support EXCEPT for ALL SEQUENCES publications
2026-05-25 07:37 UTC Peter Smith <[email protected]>
` Re: Support EXCEPT for ALL SEQUENCES publications
2026-05-25 07:37 UTC Peter Smith <[email protected]>
` Re: Support EXCEPT for ALL SEQUENCES publications
2026-05-26 06:00 UTC Shlok Kyal <[email protected]>
[3+ messages in thread]
Re: Support EXCEPT for TABLES IN SCHEMA publications
2026-05-19 11:14 UTC Nisha Moond <[email protected]>
` Re: Support EXCEPT for TABLES IN SCHEMA publications
2026-05-22 02:26 UTC Peter Smith <[email protected]>
` Re: Support EXCEPT for TABLES IN SCHEMA publications
2026-05-22 05:30 UTC Peter Smith <[email protected]>
` Re: Support EXCEPT for TABLES IN SCHEMA publications
2026-05-26 05:56 UTC Peter Smith <[email protected]>
[4+ messages in thread]
Re: problems with toast.* reloptions
2026-05-26 05:55 UTC solai v <[email protected]>
NULL pointer dereference in syslogger with load_libraries() and -DEXEC_BACKEND at startup
2026-05-25 07:45 UTC Michael Paquier <[email protected]>
` Re: NULL pointer dereference in syslogger with load_libraries() and -DEXEC_BACKEND at startup
2026-05-25 08:21 UTC Michael Paquier <[email protected]>
` Re: NULL pointer dereference in syslogger with load_libraries() and -DEXEC_BACKEND at startup
2026-05-25 08:24 UTC Ayush Tiwari <[email protected]>
` Re: NULL pointer dereference in syslogger with load_libraries() and -DEXEC_BACKEND at startup
2026-05-25 23:06 UTC Michael Paquier <[email protected]>
` Re: NULL pointer dereference in syslogger with load_libraries() and -DEXEC_BACKEND at startup
2026-05-26 02:39 UTC Euler Taveira <[email protected]>
` Re: NULL pointer dereference in syslogger with load_libraries() and -DEXEC_BACKEND at startup
2026-05-26 05:20 UTC Michael Paquier <[email protected]>
` Re: NULL pointer dereference in syslogger with load_libraries() and -DEXEC_BACKEND at startup
2026-05-26 05:39 UTC Kyotaro Horiguchi <[email protected]>
` Re: NULL pointer dereference in syslogger with load_libraries() and -DEXEC_BACKEND at startup
2026-05-26 05:52 UTC Michael Paquier <[email protected]>
[8+ messages in thread]
Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-21 06:49 UTC vignesh C <[email protected]>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-21 14:38 UTC SATYANARAYANA NARLAPURAM <[email protected]>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-22 09:15 UTC shveta malik <[email protected]>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-25 07:12 UTC SATYANARAYANA NARLAPURAM <[email protected]>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-25 09:58 UTC shveta malik <[email protected]>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-25 19:01 UTC SATYANARAYANA NARLAPURAM <[email protected]>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-26 04:36 UTC shveta malik <[email protected]>
` Re: [PATCH] Release replication slot on error in SQL-callable slot functions
2026-05-26 05:50 UTC shveta malik <[email protected]>
[8+ messages in thread]
doc: Clarify ALTER CONSTRAINT enforceability wording
2026-05-25 09:31 UTC Chao Li <[email protected]>
` Re: doc: Clarify ALTER CONSTRAINT enforceability wording
2026-05-26 05:42 UTC Chao Li <[email protected]>
[2+ messages in thread]
Re: First draft of PG 19 release notes
2026-05-26 05:25 UTC Chao Li <[email protected]>
Fix pg_get_multixact_stats() members_size calculation
2026-05-22 07:02 UTC Chao Li <[email protected]>
` Re: Fix pg_get_multixact_stats() members_size calculation
2026-05-25 08:30 UTC Michael Paquier <[email protected]>
` Re: Fix pg_get_multixact_stats() members_size calculation
2026-05-26 04:53 UTC Michael Paquier <[email protected]>
` Re: Fix pg_get_multixact_stats() members_size calculation
2026-05-26 05:17 UTC Chao Li <[email protected]>
[4+ messages in thread]
[PATCH] Little refactoring of portalcmds.c
2025-10-08 14:02 UTC Aleksander Alekseev <[email protected]>
` Re: [PATCH] Little refactoring of portalcmds.c
2025-10-27 06:02 UTC Quan Zongliang <[email protected]>
` Re: [PATCH] Little refactoring of portalcmds.c
2025-10-27 09:50 UTC wenhui qiu <[email protected]>
` Re: [PATCH] Little refactoring of portalcmds.c
2026-05-26 03:36 UTC Zizhuan Liu <[email protected]>
` Re: [PATCH] Little refactoring of portalcmds.c
2026-05-26 03:42 UTC Zizhuan Liu <[email protected]>
[5+ messages in thread]
Re: Row pattern recognition
2026-02-28 16:59 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-01 11:02 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-02 01:32 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-03 11:32 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-04 07:29 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-05 04:16 UTC 장성준 <[email protected]>
` Re: Row pattern recognition
2026-03-05 04:59 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-06 04:38 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-06 23:18 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-07 16:02 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-08 14:24 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-09 04:02 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-11 04:37 UTC SungJun Jang <[email protected]>
` Re: Row pattern recognition
2026-03-11 10:32 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-11 22:39 UTC Zsolt Parragi <[email protected]>
` Re: Row pattern recognition
2026-03-11 23:52 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-12 00:39 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-12 00:44 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-13 00:53 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-14 14:14 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-16 05:39 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-17 04:59 UTC SungJun Jang <[email protected]>
` Re: Row pattern recognition
2026-03-18 23:06 UTC Zsolt Parragi <[email protected]>
` Re: Row pattern recognition
2026-03-19 02:28 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-20 15:36 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-21 12:42 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-21 14:57 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-29 12:13 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-03-29 14:06 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-04-02 03:51 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-04-04 07:31 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-04-05 12:50 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-04-10 01:18 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-04-10 08:51 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-04-10 09:35 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-04-12 07:27 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-04-13 22:52 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-04-17 08:10 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-04-17 10:13 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-04-17 12:08 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-04-17 13:47 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-04-17 14:24 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-04-19 10:18 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-04-19 13:52 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-04-27 04:52 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-04-27 08:03 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-04-27 08:42 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-05-01 17:11 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-05-02 04:17 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-05-02 04:30 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-05-02 04:38 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-05-02 05:03 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-05-03 05:34 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-05-05 00:01 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-05-05 03:53 UTC jian he <[email protected]>
` Re: Row pattern recognition
2026-05-05 04:26 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-05-05 08:08 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-05-05 09:15 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-05-05 09:42 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-05-05 09:59 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-05-07 12:41 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-05-09 07:43 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-05-10 02:54 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-05-12 06:03 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-05-12 07:01 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-05-13 03:11 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-05-13 04:15 UTC Henson Choi <[email protected]>
` Re: Row pattern recognition
2026-05-24 08:11 UTC Tatsuo Ishii <[email protected]>
` Re: Row pattern recognition
2026-05-26 03:20 UTC jian he <[email protected]>
[69+ messages in thread]
Re: Bound memory usage during manual slot sync retries
2026-05-26 02:03 UTC Amit Kapila <[email protected]>
Re: Implement waiting for wal lsn replay: reloaded
2026-01-07 00:32 UTC Andres Freund <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-01-07 04:08 UTC Xuneng Zhou <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-01-07 08:06 UTC Alexander Korotkov <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-01-08 14:19 UTC Alexander Korotkov <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-01-08 16:29 UTC Xuneng Zhou <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-01-08 20:42 UTC Alexander Korotkov <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-01-09 13:44 UTC Xuneng Zhou <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-01-10 04:47 UTC Xuneng Zhou <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-01-12 06:53 UTC Xuneng Zhou <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-01-20 01:28 UTC Xuneng Zhou <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-01-27 01:14 UTC Xuneng Zhou <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-01-29 07:47 UTC Alexander Korotkov <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-05-19 20:00 UTC Alexander Lakhin <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-05-20 03:30 UTC Xuneng Zhou <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-05-20 05:18 UTC Xuneng Zhou <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-05-20 12:16 UTC Alexander Korotkov <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-05-23 17:09 UTC Xuneng Zhou <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-05-23 18:40 UTC Xuneng Zhou <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-05-25 09:00 UTC Alexander Korotkov <[email protected]>
` Re: Implement waiting for wal lsn replay: reloaded
2026-05-26 01:48 UTC Xuneng Zhou <[email protected]>
[20+ messages in thread]
Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-01-19 12:08 UTC Shruthi Gowda <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-03-24 02:34 UTC Mahendra Singh Thalor <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-03-24 05:59 UTC Nishant Sharma <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-04-09 10:44 UTC Shruthi Gowda <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-04-13 10:30 UTC Nishant Sharma <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-04-13 10:32 UTC Nishant Sharma <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-04-15 09:56 UTC Shruthi Gowda <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-04-16 07:04 UTC Nishant Sharma <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-04-18 16:20 UTC Shruthi Gowda <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-04-20 06:01 UTC Nishant Sharma <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-04-21 07:09 UTC Shruthi Gowda <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-04-22 04:27 UTC Nishant Sharma <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-05-01 19:20 UTC Andrew Dunstan <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-05-05 20:00 UTC Alexander Lakhin <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-05-05 20:32 UTC Tom Lane <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-05-05 21:36 UTC Andrew Dunstan <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-05-06 11:55 UTC Andrew Dunstan <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-05-06 14:58 UTC Tom Lane <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-05-06 15:50 UTC Andrew Dunstan <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-05-06 16:02 UTC Tom Lane <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-05-23 18:59 UTC SATYANARAYANA NARLAPURAM <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-05-25 07:46 UTC Shruthi Gowda <[email protected]>
` Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
2026-05-25 23:34 UTC Michael Paquier <[email protected]>
[23+ messages in thread]
Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-21 14:20 UTC Nikolay Samokhvalov <[email protected]>
` Re: Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-21 15:18 UTC Junwang Zhao <[email protected]>
` Re: Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-21 17:44 UTC Kirk Wolak <[email protected]>
` Re: Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-21 18:45 UTC Isaac Morland <[email protected]>
` Re: Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-22 15:54 UTC Tom Lane <[email protected]>
` Re: Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-24 14:22 UTC Peter Eisentraut <[email protected]>
` Re: Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-24 17:03 UTC Tom Lane <[email protected]>
` Re: Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-24 17:31 UTC Philip Alger <[email protected]>
` Re: Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-25 22:21 UTC Nikolay Samokhvalov <[email protected]>
` Re: Rename Postgres 19 to Postgres 26 (year-based)?
2026-05-25 23:28 UTC jian he <[email protected]>
[10+ messages in thread]
FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-04-07 08:42 UTC SATYANARAYANA NARLAPURAM <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-04-10 09:10 UTC jian he <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-04-10 22:00 UTC SATYANARAYANA NARLAPURAM <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-04-11 08:36 UTC jian he <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-04-15 20:59 UTC Paul A Jungwirth <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-04-17 08:13 UTC jian he <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-04-19 20:10 UTC Paul A Jungwirth <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-04-21 03:57 UTC jian he <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-04-21 14:59 UTC Paul A Jungwirth <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-04-22 01:11 UTC jian he <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-04-22 18:03 UTC Paul A Jungwirth <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-05 21:50 UTC Paul A Jungwirth <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-06 11:39 UTC Peter Eisentraut <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-06 17:13 UTC Paul A Jungwirth <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-07 01:14 UTC jian he <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-07 04:34 UTC Chao Li <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-07 05:54 UTC Chao Li <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-07 07:05 UTC Chao Li <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-07 23:26 UTC Paul A Jungwirth <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-07 23:47 UTC Paul A Jungwirth <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-08 07:09 UTC Chao Li <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-08 15:25 UTC Paul A Jungwirth <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-09 06:38 UTC Chao Li <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-11 12:03 UTC jian he <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-12 19:26 UTC Paul A Jungwirth <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-12 20:34 UTC Nathan Bossart <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-13 00:05 UTC Paul A Jungwirth <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-13 15:42 UTC Paul A Jungwirth <[email protected]>
` Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column
2026-05-25 22:23 UTC Paul A Jungwirth <[email protected]>
[29+ 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