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. -sv -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
