| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | bharath(dot)rupireddyforpostgres(at)gmail(dot)com, satyanarlapuram(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Allow async standbys wait for sync replication |
| Date: | 2022-03-01 17:05:37 |
| Message-ID: | 20220301170537.GA1031413@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 01, 2022 at 04:34:31PM +0900, Kyotaro Horiguchi wrote:
> At Mon, 28 Feb 2022 22:05:28 -0800, Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote in
>> replicated LSN. TBH there are probably other things that need to be
>> considered (e.g., how do we ensure that the WAL sender sends the rest once
>> it is replicated?), but I still think we should avoid spinning in the WAL
>> sender waiting for WAL to be replicated.
>
> It seems to me it would be something similar to
> SyncRepReleaseWaiters(). Or it could be possible to consolidate this
> feature into the function, I'm not sure, though.
Yes, perhaps the synchronous replication framework will need to alert WAL
senders when the syncrep LSN advances so that the WAL is sent to the async
standbys. I'm glossing over the details, but I think that should be the
general direction.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brar Piening | 2022-03-01 17:27:38 | Re: Add id's to various elements in protocol.sgml |
| Previous Message | Christoph Heiss | 2022-03-01 16:40:45 | Re: [PATCH] Add reloption for views to enable RLS |