References: 
 <CAPpHfdtiGgn0iS1KbW2HTam-1+oK+vhXZDAcnX9hKaA7Oe=F-A@mail.gmail.com>
 <5358d911a08ef2952b1e9f74062426ee@postgrespro.ru>
 <CAPpHfdsQNqQoFN_OosMUkZWLE-s=or=t+XVEHF5AGuMbdBMpew@mail.gmail.com>
 <CAPpHfdvZXSiVCqFNMzpk7Zhxk4hB6T55b+79J1nKLotNFL25Qw@mail.gmail.com>
 <CA+hUKGKXXP8ZgTfFfjhv77ALC-ZKcejR4pdfrfgVqYrG_75zeQ@mail.gmail.com>
 <CAPpHfdv1aXn-oUQNODQ0B6W7JC=t_S1b64V5DAx-HP+KOV-6Lg@mail.gmail.com>
 <88449be3-93e8-4d78-a0d8-c37e4cf26850@app.fastmail.com>
 <CAPpHfduGLJgQERBmQ+=bsr4Oy6F8HCVgQpCYva6=Ncib2X2oUA@mail.gmail.com>
 <8aec133e-5d7f-4fa1-8223-257647dd1ccd@app.fastmail.com>
 <CAPpHfds7M2R0PLGzGa+Y6G+n1z1Na-t5QH2Wsv9iN3n=tcFyEw@mail.gmail.com>
 <432592e4d09341d41bf5cad1df26b3f3@postgrespro.ru>
 <CAPpHfdtmbUOfNWk_ofZyQWd5kztyXhCVmUHYcSr1-JuYO0DyUw@mail.gmail.com>
 <CALj2ACUhgYVHYH5JeNKro1v+SqmDcGyNHn0smWpsQMDLikrN=w@mail.gmail.com>
 <CAPpHfdsV856ca8V=G8DFEViDP7v1hMtDUgOEdBE5dV45a3NKKw@mail.gmail.com>
 <CALj2ACWNKB2fRwaah-jv5stZcisPcwOtsOZdz6+qQWtpG=or8g@mail.gmail.com>
 <CAPpHfdtGh9Gmx-O5qhcSGJmn5z7-yFb7NGqTrM2J94E14w8EOg@mail.gmail.com>
 <87le5wa1dw.fsf@163.com>
 <CAPpHfdv4v-UrS90rSqp8wz9zsWpB7VB5bsPVAoETHWozkDwumA@mail.gmail.com>
 <87h6gk9nvc.fsf@163.com> <6eb8c9f22b075964f502080dadc16cb2@postgrespro.ru>
 <CALj2ACWDWKw5k6itqNSKwznTpa72XRoCqR4SdWqS8xM8n_zhBA@mail.gmail.com>
User-agent: mu4e 1.10.7; emacs 29.1
From: Andy Fan <zhihuifan1213@163.com>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Kartyshov Ivan <i.kartyshov@postgrespro.ru>, Alexander Korotkov
 <aekorotkov@gmail.com>, Euler Taveira <euler@eulerto.com>, Thomas Munro
 <thomas.munro@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, Amit
 Kapila <amit.kapila16@gmail.com>, Dilip Kumar <dilipbalaut@gmail.com>,
 Peter Smith <smithpb2250@gmail.com>, pgsql-hackers@lists.postgresql.org
Subject: Re: [HACKERS] make async slave to wait for lsn to be replayed
Date: Tue, 02 Apr 2024 19:43:46 +0800
In-reply-to: 
 <CALj2ACWDWKw5k6itqNSKwznTpa72XRoCqR4SdWqS8xM8n_zhBA@mail.gmail.com>
Message-ID: <87msqcc7gj.fsf@163.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/87msqcc7gj.fsf%40163.com>
Precedence: bulk


Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> writes:

> On Tue, Apr 2, 2024 at 3:41=E2=80=AFPM Kartyshov Ivan
> <i.kartyshov@postgrespro.ru> wrote:
>>
>> 8 years, we tried to add this feature, and now we suggest the best way
>> for this feature is to commit the minimal version first.
>
> Just curious, do you or anyone else have an immediate use for this
> function? If yes, how are they achieving read-after-write-consistency
> on streaming standbys in their application right now without a
> function like this?

The link [1] may be helpful and I think the reason there is reasonable
to me.

Actually we also disucss how to make sure the "read your writes
consistency" internally, and the soluation here looks good to me.

Glad to know that this patch will be committed very soon.=20

[1]
https://www.postgresql.org/message-id/CAPpHfdtuiL1x4APTs7u1fCmxkVp2-ZruXcdC=
fprDMdnOzvdC%2BA%40mail.gmail.com=20

--=20
Best Regards
Andy Fan