This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

作者 neologix
收信人 Trundle, draghuram, eric.araujo, giampaolo.rodola, neologix, pitrou, r.david.murray, tarek, techtonik, vstinner
日期 2011-09-14.06:53:41
SpamBayes Score 0.00085063226
Marked as misclassified
Message-id <1315983221.99.0.670292205036.issue8828@psf.upfronthosting.co.za>
In-reply-to
内容
> According to the following article, a fsync is also needed on the 
> directory after a rename. I don't understand if is it always needed for 
> an atomic rename, or if we only need it for the "atomic write" pattern.

It's not needed if you just want atomicity, i.e. the file is visible either under its old name or its new name, but not neither or both.
If is however needed if you want durability, i.e. you want to guarantee that the file is visible under its new name after your atomic_rename returns.
历史
日期 用户 动作 参数
2011-09-14 06:53:42neologix修改recipients: + neologix, pitrou, vstinner, draghuram, techtonik, giampaolo.rodola, tarek, eric.araujo, r.david.murray, Trundle
2011-09-14 06:53:41neologix修改messageid: <1315983221.99.0.670292205036.issue8828@psf.upfronthosting.co.za>
2011-09-14 06:53:41neologix链接issue8828 messages
2011-09-14 06:53:41neologix创建