Changes between Initial Version and Version 5 of Ticket #70556


Ignore:
Timestamp:
Aug 17, 2024, 5:16:29 PM (5 weeks ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

As of MacPorts 2.0.0, it does vacuum the registry; see [7d950c17e4be1c12ea13d487997806e5885e8f20/macports-base].

It used to do it after every operation but this was slow every time. As of MacPorts 2.9.0, it only vacuums if it's worth it, so now it's only slow at those times; see [c82a2699117181b1fedd490c62a3efffca7c8947/macports-base].

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #70556 – Description

    initial v5  
    1 I'm not the only one who has noticed or thought at times that the `port` command "hung" because apparently nothing was happening e.g. at the end of a command. I've also already had a registry corruption at least once in the past because I had interrupted (^C) a command that to the best of my recollection wasn't even one that should have touched the registry.
     1I'm not the only one who has noticed or thought at times that the `port` command "hung" because apparently nothing was happening e.g. at the end of a command. I've also already had a registry corruption at least once in the past because I had interrupted (`^C`) a command that to the best of my recollection wasn't even one that should have touched the registry.
    22
    33I know I'm also not the only one who has observed the "write-ahead log" `registry.db-wal` file getting larger than the db itself, and sometimes just persisting until for some unclear reason it disappears (which usually means one of the aforementioned "freezes").