From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Some read stream improvements |
Date: | 2025-02-26 22:19:55 |
Message-ID: | CA+hUKGKhQSBZxJhYKaWVyCTZJ5hsro_H5Op0CdJO1QzVqA6QQw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 26, 2025 at 10:55 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> I was working on expanding tests for AIO and as part of that wrote a test for
> temp tables -- our coverage is fairly awful, there were many times during AIO
> development where I knew I had trivially reachable temp table specific bugs
> but all tests passed.
>
> The test for that does trigger the problem described above and is fixed by the
> patches in this thread (which I included in the other thread):
Thanks. Alright, I'm assuming that you don't have any objections to
the way I restyled that API, so I'm going to go ahead and push some of
these shortly, and then follow up with a few newer patches that
simplify and improve the look-ahead and advice control. More very
soon.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2025-02-26 22:23:51 | Re: suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?) |
Previous Message | Tomas Vondra | 2025-02-26 22:16:13 | Re: suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?) |