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 1rrw9d-003gtD-Ko for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Apr 2024 08:39:34 +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 1rrw9c-00GmR4-Fy for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Apr 2024 08:39:32 +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 1rrw9b-00GmQw-Jp for pgsql-hackers@lists.postgresql.org; Wed, 03 Apr 2024 08:39:32 +0000 Received: from m16.mail.163.com ([220.197.31.3]) by makus.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rrw9V-000KMX-UY for pgsql-hackers@lists.postgresql.org; Wed, 03 Apr 2024 08:39:29 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=From:Subject:Date:Message-ID:MIME-Version: Content-Type; bh=9MK1kg/qroMlawC2t3IyQEXElTpF2E9qVnUwGZWe9QI=; b=PtBjOFkCkzRWhkJv5QmD/XADEzvNUNQjXT/Aju4IuXJYsASv0BU86wTo69iT3i 6uQGmyqBmqFg4pAUHuAVJYyQuamTw8S+RVmY6dlpTMCK9EJBVA6I0Lb6E3IIQm4W g70fOJLfihEEJKiekTNfeEQMHQyNuyIMq0E7lCPrFhcRk= Received: from 8235eee8a2a0 (unknown [140.205.118.32]) by gzga-smtp-mta-g2-1 (Coremail) with SMTP id _____wDnT7usFQ1mIgGhAg--.53992S3; Wed, 03 Apr 2024 16:39:09 +0800 (CST) References: <88449be3-93e8-4d78-a0d8-c37e4cf26850@app.fastmail.com> <8aec133e-5d7f-4fa1-8223-257647dd1ccd@app.fastmail.com> <432592e4d09341d41bf5cad1df26b3f3@postgrespro.ru> <87le5wa1dw.fsf@163.com> <87h6gk9nvc.fsf@163.com> <6eb8c9f22b075964f502080dadc16cb2@postgrespro.ru> <87msqcc7gj.fsf@163.com> User-agent: mu4e 1.10.7; emacs 29.1 From: Andy Fan To: Alexander Korotkov Cc: Bharath Rupireddy , Kartyshov Ivan , Euler Taveira , Thomas Munro , Peter Eisentraut , Amit Kapila , Dilip Kumar , Peter Smith , pgsql-hackers@lists.postgresql.org Subject: Re: [HACKERS] make async slave to wait for lsn to be replayed Date: Wed, 03 Apr 2024 16:36:33 +0800 In-reply-to: Message-ID: <87a5mademr.fsf@163.com> MIME-Version: 1.0 Content-Type: text/plain X-CM-TRANSID: _____wDnT7usFQ1mIgGhAg--.53992S3 X-Coremail-Antispam: 1Uf129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UbIYCTnIWIevJa73UjIFyTuYvjxUYR6zUUUUU X-Originating-IP: [140.205.118.32] X-CM-SenderInfo: x2klx3xlid0iqsrtqiywtou0bp/1tbiVBC1U2VOCL-DrAAAsR List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > I also can confirm that a lot of users would be very happy to have > "read your writes consistency" and ready to do something to achieve > this at an application level. However, they typically don't know what > exactly they need. > > So, blogging about pg_wal_replay_wait() and spreading words about it > at conferences would be highly appreciated. Sure, once it is committed, I promise I can doing a knowledge sharing in our organization and write a article in chinese language. -- Best Regards Andy Fan