On Tue, 2010-04-06 at 14:14 -0400, Seth Vidal wrote: > > On Tue, 6 Apr 2010, Adam Williamson wrote: > > > Since checking for updates is a read-only operation, does it actually > > need to lock other operations out of the database? The worst I can think > > could happen is the resulting information on available updates could be > > slightly inaccurate, but if it's made a non-blocking operation it could > > be done more frequently probably without anyone noticing, so even if it > > winds up being slightly off for a bit, it would fairly quickly be fixed. > > > checking for updates isn't read-only. It's downloading new metadata. Now, > for the user-run - it's fine - but for root-run - it needs to lock. However, we already established that the problem case is when it runs right after you've done a yum operation, in which case the metadata has already just been refreshed, and it should be using the already-cached metadata. In that case, does it need to lock? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
