Re: [PATCH 0/5] reftable: fix writing multi-level indices

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 26, 2024, 16:26 UTC
Message-ID: <xmqqy1ccnjs3.fsf@gitster.g>
In-Reply-To: <cover.1706263918.git.ps@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

> yesterday I noticed that writing reftables with more than 250,000 refs
> led to the last block of refs in the table not being seekable anymore.
> As it turns out, 250k refs was the boundary at which we start to write
> multi-level indices for refs.

Obviously one of the less exercised corners of the code ;-)

> The topic depends on Junio's jc/reftable-core-fsync at 1df18a1c9a
> (reftable: honor core.fsync, 2024-01-23) due to a semantic merge
> conflict in the newly added test.

Thanks for the note for the base. John Cai's work is well done and has been reviewed, so let's merge it down to 'next' soonish.

Thanks.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.