Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tp1iK-00HCp3-6z for pgsql-hackers@arkaria.postgresql.org; Mon, 03 Mar 2025 09:03:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tp1iI-002I0Q-Ia for pgsql-hackers@arkaria.postgresql.org; Mon, 03 Mar 2025 09:03:50 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tp1iI-002I0I-6m for pgsql-hackers@lists.postgresql.org; Mon, 03 Mar 2025 09:03:50 +0000 Received: from mail1.dalibo.net ([51.159.93.128] helo=mail.dalibo.com) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tp1iF-000gP8-2P for pgsql-hackers@lists.postgresql.org; Mon, 03 Mar 2025 09:03:49 +0000 Received: from [192.168.1.18] (unknown [90.58.191.166]) by mail.dalibo.com (Postfix) with ESMTPSA id 20129262BD; Mon, 3 Mar 2025 10:03:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dalibo.com; s=a; t=1740992625; bh=qiaYrszSOgymPfvZbWnDUNPUGn3gQbJ6HWzoOY5ddYo=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=NAZKZB3N3bUSX671fGfqSOJ579kaVnsAGwvmbhb1TVT8v5bhAboszJofUAqQ897vb rsdi5XVe1SpWgaI6lrFDkNJqAr1Bxfi5iGr6MzUWEUJyq43G6maU/X2GybZdBF3LRQ 7H/4qgtTvm8oeooXp6Mz/IE/c4sl8XzFRM+qn/GE= Message-ID: Date: Mon, 3 Mar 2025 10:03:44 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: long-standing data loss bug in initial sync of logical replication To: "Zhijie Hou (Fujitsu)" , Amit Kapila Cc: Shlok Kyal , vignesh C , Nitin Motiani , Andres Freund , PostgreSQL Hackers , Masahiko Sawada References: <2e2b2aba-c285-4bfc-a3bd-c55ac2df9568@dalibo.com> Content-Language: fr From: =?UTF-8?Q?Benoit_Lobr=C3=A9au?= Autocrypt: addr=benoit.lobreau@dalibo.com; keydata= xsBNBF3FR7IBCADDvtR0p09SI9OvnbWw+VEvO5IXefBWFWefxrPd0H3Sf3gsBLiKbRdkSjvz 2y+ksRgBUkhK1Kiqe/QuddgvuT9OUFBCrOtZxkBgJYRbxBNTOnIehhEoK9sdqjwvwNyxJUEX er1UgErP+MJTvwpW1J8Uq9oV+NbqgNQ7ca5G2D3x7DI2Tbbw0iu+lmCIdXQpTk7hacErGscC p/eaJQFd6EPAZPS7BQEgjuDDjGCy4RzTSiobtqn0ocaEj+w7365FVKKZD2LjEm1mfBK/4nml H/vlssXkKKpUGetaib6AVpZK3a0xBTMi04ft/V8iGGJuVhE45WjjKSckmeLafTZCGxN9ABEB AAHNK0Jlbm9pdCBMb2Jyw6lhdSA8YmVub2l0LmxvYnJlYXVAZGFsaWJvLmNvbT7CwJQEEwEI AD4CGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AWIQRkbHJAht3VPY+ptaDDJY+vq0O76wUC Za56QgUJC6uZkAAKCRDDJY+vq0O760ECCACDPj6p9VXaX4GF9p+3zhoDwxsUWh0xODwsK//h SBGsRmPaElApbOR5rs2WDFaPE95XG3Vdo2rno7i4mt0fASls7vq4P0BPJiPM4fKEr+kfXAxP 2clqmkBMn2o+EEeUGDmnn3RAVzDDoyML6N/unpyOTHWfscxvvj6AKreUtxzQm0LVQRL+hIaG SAlcwpVWQBPhA6Roi1/7Uz9qm8nWjFOuV6vO5yVe0sfRrrO9AFkjBGFT/B06sSs33Os6Hjs5 2ckLn5Gxlty8XgTpbaG0bJiV+GDTcXh5UV8XVKaMomOLJxWw8US6PSSqQxodWuJqsvlxXV93 ae6cMIosHsriaUo5zsBNBF3FR7IBCADEWwsQar1qtLKdoAoqKThz+kQXu3UADQ0c8JCgsp+8 a6hFDg+uIw0j852lkJOPHll414Qw+kLC1bUo7H6+mPHzko/aR3TFz6vvOrm0afwFP7sm9Vbe UbpeohnrXBBwb1PjNhDphaXeMVovJqSgRifhc/sAR6fXi+2OCrH+8CUYa0aHhwoecStgw/tm EDPZ8lCsg5IdyO5Er4ZMOl/EbaRuTOpl7U/GzJBQSYf7t4KHotIpEeuJVv4X/+nTW3ALG+dG pRA5GplNnlQNfsEymnT4W7RbfafDp7Q7nK6w7d55ZU8UyiS6N/1wh/DL1hntC65lQbHlmwNx RG132ecNOcqFABEBAAHCwHwEGAEIACYCGwwWIQRkbHJAht3VPY+ptaDDJY+vq0O76wUCZa56 dQUJC6uZwwAKCRDDJY+vq0O76y9jB/0fVyz7D56D2A6MUGASNkh6IiuHCF/UgEfU0m5fC6pd 38+fmyUMkGR3QwrtZP3SCLaBKT4LHxhVu7tEUWI+6WK7/s0Jsx5L8aIfDKY4zjqQ9InP+LkA azkKW4JpIb9Ny0FzRjUyf9gReU5nMy9sUNS4DhoHG6c/bQYqkj9uA5AokiDDCRg2dobfpaNP C6qQQIXD+wi0aZ4jR5r4rXMxmwFutandoaxDpPBj4EXlyRHhzyKfgb2c6TXdCVQ5YJUFUi9k gl7CXplN8vBpMuzN5y6NPd3Xekcp16D5XCQNBQ2drIsnFR4IbDPI1Mqd6OJYH0vum6g8FmoN s7ygc4oi12nU In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 3/3/25 8:41 AM, Zhijie Hou (Fujitsu) wrote: > A nitpick with the data for the Concurrent Transaction (2000) case. The results > show that the HEAD's data appears worse than the patch data, which seems > unusual. However, I confirmed that the details in the attachment are as expected, > so, this seems to be a typo. (I assume you intended to use a > decimal point instead of a comma in the data like (8,43500...)) Hi, Argh, yes, sorry! I didn't pay enough attention and accidentally inverted the Patch and Head numbers in the last line when copying them from the ODS to the email to match the previous report layout. The comma is due to how decimals are written in my language (comma instead of dot). I forgot to "translate" it. Concurrent Txn | Head (sec) | Patch (sec) | Degradation in % --------------------------------------------------------------------- 50 | 0.1797647 | 0.1920949 | 6.85907744957 100 | 0.3693029 | 0.3823425 | 3.53086856344 500 | 1.62265755 | 1.91427485 | 17.97158617972 1000 | 3.01388635 | 3.57678295 | 18.67676928162 2000 | 6.4713304 | 7.0171877 | 8.43500897435 > as Amit pointed out, we will share a new test script soon > that uses the SQL API xxx_get_changes() to test. It would be great if you could > verify the performance using the updated script as well. Will do. -- Benoit Lobréau Consultant http://dalibo.com