[Yum-devel] [PATCH 1/3] Add dropCachedDataPostTransaction() API and document dropCachedData().

Tim Lauridsen tim.lauridsen at gmail.com
Sat Sep 25 06:08:57 UTC 2010


On Fri, Sep 24, 2010 at 11:31 PM, seth vidal <skvidal at fedoraproject.org>wrote:

> On Fri, 2010-09-24 at 00:02 -0400, James Antill wrote:
> > Calling dropCachedData() before we are "done" is pretty bad, as we can
> > load a package more than once. It's also a giant perf. hit, esp. for
> > yumdb checksum*. So we Document all that and add a special API to call
> > just after a transaction has run, to cleanup just the stuff we want.
>
>
> ACK - but I sometimes wonder if moving the yumdb to sqlite would be
> better until/if we move to btrfs for the fs
>
> -sv
>
>
> _______________________________________________
> Yum-devel mailing list
> Yum-devel at lists.baseurl.org
> http://lists.baseurl.org/mailman/listinfo/yum-devel
>

I remember there was some discussion about sqlite vs. filesystem as a db for
yumdb, but cant remember why it sqlite was not selected in the first place.
Can some one enlighten my "old" brain" :)

Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.baseurl.org/pipermail/yum-devel/attachments/20100925/28db8aae/attachment.html>


More information about the Yum-devel mailing list