=?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@xbc.nu> writes:
> Ben Collins-Sussman wrote:
>
> >This user sent me a copy of his repository. But I can't read the DB
> >files on my Intel machine, due to endianness problems. The user then
> >sent me dump files of his six tables, produced by 'db_dump'. However,
> >I can't 'db_load' those -- I run out of locks and memory when I try
> >(even when I set the maximum locks in DB_CONFIG from 2000 to 20000!).
> >Cmpilato points out that db_loading probably wouldn't work anyway,
> >since we depend on custom sorting routines which db_load wouldn't be
> >using.
> >
> >
>
> What?! We needed custom sorting in the Bad Old Days, to sort the node
> IDs so that relatedness checks were faster. In these Enlightened Times
> of the New Schema, no such customization should be necessary. Please
> tell me that we're really not using custom sort algorithms any more, so
> that db_dump and db_load can work.
>
> Otherwise we'll need another repository reload before 1.0.
The custom sorting is still present. We sort by NODE_ID, then
COPY_ID, then TXN_ID. But it occurs to me that all we really need
nowadays is the `next-id' for determining the NODE-ID (just like the
other tables). The only thing that expects the sorted table is the
guy who generates new NODE-IDs.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 25 19:56:45 2002