Re: [BUG] Crash on pgbench initialization. - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [BUG] Crash on pgbench initialization.
Date
Msg-id 20230725032411.47qialan3n5hjrh6@awork3.anarazel.de
Whole thread Raw
In response to Re: [BUG] Crash on pgbench initialization.  (Andres Freund <andres@anarazel.de>)
Responses Re: [BUG] Crash on pgbench initialization.
List pgsql-hackers
Hi,

On 2023-07-24 09:42:44 -0700, Andres Freund wrote:
> > I don't know this code at all, but I hope that this can be solved with
> > just Anton's proposed patch.
> 
> Yes, it's just that off-by-one.  I need to check if there's a similar bug for
> local / temp table buffers though.

Doesn't appear that way. We *do* fail if there's only 1 remaining buffer, but
we already did before my change (because we also need to pin the fsm). I don't
think that's an issue worth worrying about, if all-1 of local buffers are
pinned, you're going to have problems.

Thanks Anton / Victoria for the report and fix. Pushed.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: "Mr.Bim"
Date:
Subject: Partition pruning not working on updates
Next
From: Andres Freund
Date:
Subject: Re: Performance degradation on concurrent COPY into a single relation in PG16.