Re: FSM Corruption (was: Could not read block at end of the relation) - Mailing list pgsql-bugs

From Ronan Dunklau
Subject Re: FSM Corruption (was: Could not read block at end of the relation)
Date
Msg-id 6055942.lOV4Wx5bFT@aivenlaptop
Whole thread Raw
In response to Re: FSM Corruption (was: Could not read block at end of the relation)  (Ronan Dunklau <ronan.dunklau@aiven.io>)
Responses Re: FSM Corruption (was: Could not read block at end of the relation)  (Noah Misch <noah@leadboat.com>)
List 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@GLIBC_2.2.5

Without the patch:

   0.01%  postgres  libc.so.6          [.] llseek@GLIBC_2.2.5


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

Regards,

--
Ronan





pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18417: Excessive log messages on warm standby server
Next
From: Laurenz Albe
Date:
Subject: Re: BUG #18416: Confirmation of Issue with PostgreSQL ODBC Driver for Windows