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 1rrUpw-000xpK-UP for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Apr 2024 03:29:26 +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 1rrUpv-0048a9-Be for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Apr 2024 03:29:24 +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 1rrUpu-0048a1-JI for pgsql-hackers@lists.postgresql.org; Tue, 02 Apr 2024 03:29:23 +0000 Received: from m15.mail.163.com ([45.254.50.220]) by makus.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rrUpp-0004cg-T9 for pgsql-hackers@lists.postgresql.org; Tue, 02 Apr 2024 03:29:21 +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=jqiBPECLxKSzPjt1Rj0iJnh9z13IDmeWjwWy4cipXx4=; b=EoN3c+onVZ9uE1cpkN7F/9hDv2K0KPPG6NzEH4QQtMJZqYiAGht4CPx0DPTgbC Yp833zzmF98puwiUBhKDZEzBcVJa0eEMzHp20avuv54t1XxjYPnzKhOTLeP2EacD lGzysFJ8t/2rdJyUQrHnqbIZExEwcuquho2vlyeBMOANY= Received: from 8235eee8a2a0 (unknown [140.205.118.106]) by gzga-smtp-mta-g0-3 (Coremail) with SMTP id _____wCnFiV7ewtmVdtkDA--.56542S3; Tue, 02 Apr 2024 11:28:59 +0800 (CST) References: <5358d911a08ef2952b1e9f74062426ee@postgrespro.ru> <88449be3-93e8-4d78-a0d8-c37e4cf26850@app.fastmail.com> <8aec133e-5d7f-4fa1-8223-257647dd1ccd@app.fastmail.com> <432592e4d09341d41bf5cad1df26b3f3@postgrespro.ru> 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: Tue, 02 Apr 2024 11:25:57 +0800 In-reply-to: Message-ID: <87le5wa1dw.fsf@163.com> MIME-Version: 1.0 Content-Type: text/plain X-CM-TRANSID: _____wCnFiV7ewtmVdtkDA--.56542S3 X-Coremail-Antispam: 1Uf129KBjvdXoW7JF47Zw4rGw4DGr4rtF1xuFg_yoW3Xrg_XF nxXw1jgFZ0qF1DA3Z3Ka1fJr43WFWDXa4jga4UXanxGrykWwnFy3WvqryfXFWxXryxCr1Y kFnIkwsFy3W2gjkaLaAFLSUrUUUUjb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUvcSsGvfC2KfnxnUUI43ZEXa7IUUDPEDUUUUU== X-Originating-IP: [140.205.118.106] X-CM-SenderInfo: x2klx3xlid0iqsrtqiywtou0bp/1tbiVBi0U2VOCKqXhwABsz List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Alexander Korotkov writes: Hello, > > Did you forget to attach the new patch? > > Yes, here it is. > > ------ > Regards, > Alexander Korotkov > > [4. text/x-diff; v17-0001-Implement-pg_wal_replay_wait-stored-procedure.patch]... + + pg_wal_replay_wait ( + target_lsn pg_lsn, + timeout bigint DEFAULT 0) + void + Should we return the millseconds of waiting time? I think this information may be useful for customer if they want to know how long time it waits for for minitor purpose. -- Best Regards Andy Fan