Re: Fix an incorrect assertion condition in mdwritev().

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Xing Guo <higuoxing@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2024-05-26T00:22:06Z
Lists: pgsql-hackers
On Sat, May 25, 2024 at 11:52:22PM +0800, Xing Guo wrote:
> In commit 4908c58[^1], a vectored variant of smgrwrite() is added and
> the assertion condition in mdwritev() no longer matches the comment.
> This patch helps fix it.
>
>  	/* This assert is too expensive to have on normally ... */
>  #ifdef CHECK_WRITE_VS_EXTEND
> -	Assert(blocknum < mdnblocks(reln, forknum));
> +	Assert(blocknum + nblocks <= mdnblocks(reln, forknum));
>  #endif

Yes, it looks like you're right that this can be made stricter,
computing the number of blocks we're adding in the number calculated
(aka adding one block to this number fails immediately at initdb).
--
Michael

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Improve assertion in mdwritev()

  2. Provide vectored variants of smgrread() and smgrwrite().