5 ms·
You mean lose data after it's been committed. I can send something to the database just as it's dying and it's been lost.
by dalore 13y ago
You mean lose data after it's been committed. I can send something to the database just as it's dying and it's been lost.
- fulafel 13y agoSQL commit is not allowed to finish before the data is safely on disk (that's the D in ACID).
- icebraining 13y agoThat's assuming that the RDBMS can tell. The disks may lie:|
- plorg 13y agoThus the 's' in reisub?
- kelnos 13y agoThe disk may lie. The 's' will get the OS to send everything out to the disk. Actually writing it to the platter (or flash part, or whatever) is at the disk's discretion.
- fulafel 13y agoIt's at the disk's discretion as far as the laws of physics are concerned, but this would a severely broken disk prone to losing data and if it was a major server disk vendor, the vendor would take a pretty serious hit to its reputation.
- fulafel 13y agoOr the CPU or the memory or the OS...
- Filligree 13y agoYou should strive not to use such disks in your server. A machine reset won't power off the disks, though.
- dalore 13y agoYes, but my point was that I could send data to an ACID compliant server, and kill it before the commit happened and data will be lost. Just trying to point out to the parent poster that sending is not enough, you need to wait for the commiting.