losses - Search results in mailing lists
Mailing lists >> pgsql-bugs >> Thread
2025-04-28 07:57:47 | Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load (vignesh C)
loss. As an alternative, we could set recovery_target_inclusive to false in the setup
Mailing lists >> pgsql-bugs >> Thread
2025-03-13 23:52:49 | CHECK that involves a function call behaves differently during bulk load? (Kirk Parker)
loss about how to even go about troubleshooting this. Since valid_upc_ean() is a pure
Mailing lists >> pgsql-bugs >> Thread
2024-12-10 21:08:09 | Re: pg_dump crash on identity sequence with not loaded attributes (Tom Lane)
away that whole optimization, which has got to be an overall loss. regards, tom lane
Mailing lists >> pgsql-bugs >> Thread
2024-11-08 08:10:54 | Re: BUG #18692: Segmentation fault when extending a varchar column with a gist index with (Tom Lane)
loss; b) the two inputs have probably come through similar paths (eg, both are fresh
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (4)
2024-10-09 13:44:31 | Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior. (vignesh C)
loss or duplication. This is because the + publisher replicates changes as the partitioned table after
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (40)
2024-07-12 03:42:07 | Re: Potential data loss due to race condition during logical replication slot creation (Michael Paquier)
On Fri, Jul 12, 2024 at 11:52:20AM +0900, Masahiko Sawada wrote: Thanks, Sawada
Mailing lists >> pgsql-bugs >> Thread
2024-05-16 16:58:29 | Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption (Tom Lane)
there are, let's just cut our losses and not do it. regards, tom lane
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (5)
2024-05-07 11:31:36 | Re: BUG #18457: Possible data loss needs to be evaluated (Julius Ernesti)
loss needs to be evaluated On Tue, 2024-05-07 at 08:35 +0000, PG Bug reporting
Mailing lists >> pgsql-bugs >> Thread
2024-04-17 14:42:39 | Re: BUG #18411: Unable to create database with owner on AWS RDS (Myka Dresser)
loss as to whether: - I have hit a bug with the "CREATE DATABASE my_database
Mailing lists >> pgsql-bugs >> Thread
2024-03-16 03:03:39 | Re: FSM Corruption (was: Could not read block at end of the relation) (Noah Misch)
loss. A persistent error in an innocent INSERT is unacceptable, and the alternatives we discussed
Mailing lists >> pgsql-bugs >> Thread
2023-12-24 17:16:31 | Re: BUG #18240: Undefined behaviour in cash_mul_flt8() and friends (Jonathan S. Katz)
loss of precision"[1], but I do agree with the concerns on a pg_upgrade
Mailing lists >> pgsql-bugs >> Thread
2023-12-01 14:20:28 | Re: BUG #17948: libpq seems to misbehave in a pipelining corner case (Alvaro Herrera)
loss is because we're consuming elements from the command queue even when we shouldn
Mailing lists >> pgsql-bugs >> Thread
2023-11-29 08:45:09 | Re: BUG #18216: Unaccent function is unable to remove accents (diacritic signs) from Japanese character (Pavel Stehule)
loss and the meaning of the world should be based only on context. Žár (the heat
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2023-11-19 21:15:37 | AW: BUG #18205: Performance regression with NOT NULL checks. (Daniel Migowski)
performance win shows a loss this big on a (presumably) real-world case. regards, tom lane
Mailing lists >> pgsql-bugs >> Thread
2023-11-15 18:11:32 | Re: BUG #18196: Databases Created in Turkish Language Will Not Run on the Latest Version (Halil Han Badem)
loss. Note: After updating Windows, if you reinstall PostgreSQL, you will see that all Turkish