Re: Allow reading LSN written by walreciever, but not flushed yet

From: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Allow reading LSN written by walreciever, but not flushed yet
Date: 2025-05-13 20:11:49
Message-ID: CADzfLwU1vTQJZs2xZxoDvB3aggaDu7d2d2-wjzoW1aYJkqPSpA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello, everyone!

> Or might want LSN "flush everything you have written, and return that LSN". That will also do the trick, but is not necessary.
I think it is a better option. Less things may go wrong in such a case.

Best regards,
Mikhail.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Florents Tselai 2025-05-13 20:24:11 Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part
Previous Message Salvatore Dipietro 2025-05-13 18:37:45 Re: Remove Instruction Synchronization Barrier in spin_delay() for ARM64 architecture