atchset doesn't contain libaio support and I am not planning to
> work on using libaio. Nor do I think it makes sense for anybody else to do so
> - libaio doesn't work for buffered IO, making it imo not particularly useful
> for us.
>
> The io_uring specific code isn't
irrecoverability exists (even if rare), we would like to
discuss the possibility of back-patching this fix.
Are there any technical reasons not to back-patch this fix to older
major versions?
Thank you for your consideration.
Sincerely,
Robert Pang
[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a
Dear Michael,
Thank you for applying this back-patch. I also appreciate everyone's input
on this issue.
Sincerely,
Robert Pang
On Thu, Dec 19, 2024 at 4:13 PM Michael Paquier wrote:
> On Thu, Dec 19, 2024 at 11:07:25AM -0500, Andres Freund wrote:
> > On 2024-12-19 09:31:14
On Wed, Jan 15, 2025 at 12:05 PM Andres Freund wrote:
>
> If you have wal_recycle=true, this overhead will only be paid the first time a
> WAL segment is used, of course, not after recycling.
Today, our pg_stat_wal view [1] does not report the no. of WAL
segments recycled. How about if we add a c
do others think?
On Fri, Jan 24, 2025 at 7:22 AM Hannu Krosing wrote:
> On Wed, Jan 22, 2025 at 10:18 PM Robert Pang
> wrote:
> >
> > On Wed, Jan 15, 2025 at 12:05 PM Andres Freund
> wrote:
> > >
> > > If you have wal_recycle=true, this overhead will only
