pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18554: pg_verifybackup is not work
2024-07-26 11:56 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18554: pg_verifybackup is not work
2024-07-26 17:52 UTC Zaid Shabbir <zaidshabbir@gmail.com>
[2+ messages in thread]
BUG #18552: slow query, but using union is ok.
2024-07-25 09:53 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18552: slow query, but using union is ok.
2024-07-25 12:06 UTC David Rowley <dgrowleyml@gmail.com>
[2+ messages in thread]
BUG #18550: Cross-partition update of a former inheritance parent leads to an assertion failure
2024-07-23 13:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18550: Cross-partition update of a former inheritance parent leads to an assertion failure
2024-07-23 16:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18550: Cross-partition update of a former inheritance parent leads to an assertion failure
2024-07-23 17:21 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18550: Cross-partition update of a former inheritance parent leads to an assertion failure
2024-07-23 19:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18550: Cross-partition update of a former inheritance parent leads to an assertion failure
2024-07-24 10:44 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[5+ messages in thread]
BUG #18549: Support ipv6 link-local addresses in the inet type
2024-07-22 16:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18549: Support ipv6 link-local addresses in the inet type
2024-07-22 16:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18549: Support ipv6 link-local addresses in the inet type
2024-07-23 22:18 UTC Johannes Ernst <git@j12t.org>
[3+ messages in thread]
BUG #18533: pg_basebackup uses out-of-bounds memory and a segment error occurs during backup
2024-07-12 07:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18533: pg_basebackup uses out-of-bounds memory and a segment error occurs during backup
2024-07-23 21:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
[PATCH] Reset relhassubclass when attaching as a partition
2024-07-23 16:49 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
BUG #18551: pg_basebackup uses out-of-bounds memory and a segment error occurs during backup
2024-07-23 15:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18551: pg_basebackup uses out-of-bounds memory and a segment error occurs during backup
2024-07-23 16:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
A generated column cannot be part of a partition key
2024-07-22 22:37 UTC Diego Stammerjohann <diegostammer@gmail.com>
` Re: A generated column cannot be part of a partition key
2024-07-23 11:55 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: A generated column cannot be part of a partition key
2024-07-23 12:01 UTC Diego Stammerjohann <diegostammer@gmail.com>
` Re: A generated column cannot be part of a partition key
2024-07-23 13:31 UTC Erik Wienhold <ewie@ewie.name>
` Re: A generated column cannot be part of a partition key
2024-07-23 13:57 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: A generated column cannot be part of a partition key
2024-07-23 14:01 UTC Diego Stammerjohann <diegostammer@gmail.com>
` Re: A generated column cannot be part of a partition key
2024-07-23 14:18 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: A generated column cannot be part of a partition key
2024-07-23 14:51 UTC Peter Eisentraut <peter@eisentraut.org>
[8+ messages in thread]
BUG #18546: Attempt to insert default into a non-updatable column of a view fails with a dubious error
2024-07-20 09:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18546: Attempt to insert default into a non-updatable column of a view fails with a dubious error
2024-07-20 16:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18546: Attempt to insert default into a non-updatable column of a view fails with a dubious error
2024-07-22 08:41 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18546: Attempt to insert default into a non-updatable column of a view fails with a dubious error
2024-07-22 14:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
回复: [External]Re: BUG #18540: Does PG16 standby database support function pg_replication_origin_advance?
2024-07-22 02:51 UTC Jason ChenTJ (CN) <Jason.ChenTJ@homecredit.cn>
BUG #18547: bemused by your unhelpful installation guides
2024-07-20 22:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18547: bemused by your unhelpful installation guides
2024-07-21 16:52 UTC Christophe Pettus <xof@thebuild.com>
` Re: BUG #18547: bemused by your unhelpful installation guides
2024-07-21 19:39 UTC David G. Johnston <david.g.johnston@gmail.com>
[3+ messages in thread]
BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-11 06:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-11 10:22 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-11 15:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-12 03:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-12 09:03 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-12 10:37 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-12 12:01 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-12 14:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-16 09:19 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-16 15:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-24 17:16 UTC Jonathan S. Katz <jkatz@postgresql.org>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-24 18:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-25 00:52 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-25 01:09 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-25 09:57 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2023-12-25 15:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2024-01-11 01:12 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2024-01-12 16:19 UTC Jonathan S. Katz <jkatz@postgresql.org>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2024-01-12 16:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2024-01-13 03:50 UTC Jonathan S. Katz <jkatz@postgresql.org>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2024-01-14 00:55 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2024-01-15 07:54 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2024-07-19 14:44 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends
2024-07-19 17:06 UTC Nathan Bossart <nathandbossart@gmail.com>
[24+ messages in thread]
BUG #18544: Setting local config_parameter to DEFAULT behaves unexpectedly when using period in config name
2024-07-18 09:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18544: Setting local config_parameter to DEFAULT behaves unexpectedly when using period in config name
2024-07-18 11:46 UTC Aleksander Alekseev <aleksander@timescale.com>
` Re: BUG #18544: Setting local config_parameter to DEFAULT behaves unexpectedly when using period in config name
2024-07-18 11:58 UTC Hayden Sim <haydenwillsim@gmail.com>
` Re: BUG #18544: Setting local config_parameter to DEFAULT behaves unexpectedly when using period in config name
2024-07-18 13:53 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18544: Setting local config_parameter to DEFAULT behaves unexpectedly when using period in config name
2024-07-18 13:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18544: Setting local config_parameter to DEFAULT behaves unexpectedly when using period in config name
2024-07-19 02:39 UTC Hayden Sim <haydenwillsim@gmail.com>
` Re: BUG #18544: Setting local config_parameter to DEFAULT behaves unexpectedly when using period in config name
2024-07-19 13:17 UTC David G. Johnston <david.g.johnston@gmail.com>
[7+ messages in thread]
BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
2023-04-06 18:42 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
2023-04-07 09:16 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
2023-04-29 11:36 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
2023-04-29 11:42 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
2023-04-29 22:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
2024-07-05 12:49 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
2024-07-15 10:51 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
2024-07-15 13:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
2024-07-15 19:45 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
2024-07-15 20:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
2024-07-16 10:29 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
2024-07-19 04:45 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
[12+ messages in thread]
BUG #18543: Mistake in docs example
2024-07-17 12:53 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18543: Mistake in docs example
2024-07-17 19:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
libpq: unexpected return code from PQexecParams with a DO INSTEAD rule present
2024-07-14 15:39 UTC Vasilii Smirnov <vasilii.smirnov@mailbox.org>
` Re: libpq: unexpected return code from PQexecParams with a DO INSTEAD rule present
2024-07-15 14:04 UTC Aleksander Alekseev <aleksander@timescale.com>
` Re: libpq: unexpected return code from PQexecParams with a DO INSTEAD rule present
2024-07-17 13:58 UTC Aleksander Alekseev <aleksander@timescale.com>
` Re: libpq: unexpected return code from PQexecParams with a DO INSTEAD rule present
2024-07-17 17:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
RE：BUG #18533: pg_basebackup uses out-of-bounds memory and a segment error occurs during backup
2024-07-17 14:55 UTC 1165125080 <1165125080@qq.com>
BUG #18542: Order by expression, that contains column from projection isn't working
2024-07-16 09:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18542: Order by expression, that contains column from projection isn't working
2024-07-16 12:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18540: Does PG16 standby database support function pg_replication_origin_advance?
2024-07-15 08:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18540: Does PG16 standby database support function pg_replication_origin_advance?
2024-07-16 01:00 UTC Michael Paquier <michael@paquier.xyz>
[2+ messages in thread]
BUG #18531: err when using 'current of' with incremental COMMIT
2024-07-09 11:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18531: err when using 'current of' with incremental COMMIT
2024-07-15 16:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18536: Using WITH inside WITH RECURSIVE triggers a "shouldn't happen" error
2024-07-13 09:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18536: Using WITH inside WITH RECURSIVE triggers a "shouldn't happen" error
2024-07-14 15:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18536: Using WITH inside WITH RECURSIVE triggers a "shouldn't happen" error
2024-07-14 17:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18536: Using WITH inside WITH RECURSIVE triggers a "shouldn't happen" error
2024-07-14 17:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18536: Using WITH inside WITH RECURSIVE triggers a "shouldn't happen" error
2024-07-15 12:16 UTC Aleksander Alekseev <aleksander@timescale.com>
` Re: BUG #18536: Using WITH inside WITH RECURSIVE triggers a "shouldn't happen" error
2024-07-15 12:17 UTC Aleksander Alekseev <aleksander@timescale.com>
[6+ messages in thread]
BUG #18534: ERROR: portal "C_n" does not exist type of error getting thrown.
2024-07-12 09:31 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18534: ERROR: portal "C_n" does not exist type of error getting thrown.
2024-07-15 11:23 UTC Aleksander Alekseev <aleksander@timescale.com>
[2+ messages in thread]
BUG #18156: Self-referential foreign key in partitioned table not enforced on deletes
2023-10-13 14:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18156: Self-referential foreign key in partitioned table not enforced on deletes
2024-01-24 17:52 UTC Matthew Gabeler-Lee <fastcat@gmail.com>
` Re: BUG #18156: Self-referential foreign key in partitioned table not enforced on deletes
2024-07-12 12:36 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[3+ messages in thread]
BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-09 06:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-10 07:50 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-12 05:49 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-12 06:12 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-12 06:44 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-12 09:19 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-19 04:29 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-27 13:54 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-27 14:01 UTC Daniel Westermann (DWE) <daniel.westermann@dbi-services.com>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-27 14:55 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-27 18:41 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-28 00:18 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-28 09:17 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-28 10:59 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-28 11:27 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-29 00:15 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-29 04:37 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-29 17:56 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-06-29 19:10 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-07-03 18:21 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-07-04 07:57 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-07-04 12:17 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-07-05 02:24 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
2024-07-12 10:57 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[24+ messages in thread]
Potential data loss due to race condition during logical replication slot creation
2024-02-01 22:28 UTC Callahan, Drew <callaan@amazon.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-02-02 00:53 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-02-03 03:12 UTC Callahan, Drew <callaan@amazon.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-02-03 13:48 UTC vignesh C <vignesh21@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-02-05 02:06 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-02-05 02:12 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-02-08 05:54 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-02-19 09:12 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: Potential data loss due to race condition during logical replication slot creation
2024-03-13 09:34 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` RE: Potential data loss due to race condition during logical replication slot creation
2024-03-13 09:47 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-03-18 09:08 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-03-18 09:18 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: Potential data loss due to race condition during logical replication slot creation
2024-03-19 02:16 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-03-19 02:33 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: Potential data loss due to race condition during logical replication slot creation
2024-03-19 04:39 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-03-19 16:42 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: Potential data loss due to race condition during logical replication slot creation
2024-03-27 07:54 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-03-27 08:26 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: Potential data loss due to race condition during logical replication slot creation
2024-03-27 10:37 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-04-16 03:56 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-06-20 06:19 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-06-21 06:46 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-06-24 03:54 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-06-24 05:01 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-06-25 04:24 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-06-25 08:26 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-06-26 09:17 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-07-05 14:52 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-07-07 23:56 UTC Michael Paquier <michael@paquier.xyz>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-07-08 03:01 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: Potential data loss due to race condition during logical replication slot creation
2024-07-08 09:01 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-07-08 14:02 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-07-09 05:29 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-07-09 09:27 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-07-10 01:15 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-07-10 02:21 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-07-10 03:43 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-07-10 05:30 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-07-12 02:52 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Potential data loss due to race condition during logical replication slot creation
2024-07-12 03:42 UTC Michael Paquier <michael@paquier.xyz>
[40+ messages in thread]
[next (older)]
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox