Re: FSM Corruption (was: Could not read block at end of the relation)

From: Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: FSM Corruption (was: Could not read block at end of the relation)
Date: 2024-03-29 08:47:52
Message-ID: 6055942.lOV4Wx5bFT@aivenlaptop
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Le jeudi 21 mars 2024, 14:51:25 CET Ronan Dunklau a écrit :
> Le samedi 16 mars 2024, 05:58:34 CET Noah Misch a écrit :
> > > - Get profiles with both master and patched. (lseek or freespace.c
> > > functions>
> > >
> > > rising by 0.1%-1% would fit what we know.)

Running perf during the same benchmark, I get the following samples for lseek:

With the patch:

0.02% postgres libc.so.6 [.] llseek(at)GLIBC_2(dot)2(dot)5

Without the patch:

0.01% postgres libc.so.6 [.] llseek(at)GLIBC_2(dot)2(dot)5

So nothing too dramatic.
I haven't been able to come up with a better benchmark.

Regards,

--
Ronan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Laurenz Albe 2024-03-29 08:57:15 Re: BUG #18416: Confirmation of Issue with PostgreSQL ODBC Driver for Windows
Previous Message PG Bug reporting form 2024-03-29 04:44:27 BUG #18417: Excessive log messages on warm standby server