On 2/27/07, Josh Berkus <josh@agliodbs.com> wrote:
It seriously narrows down the problem space to know that PostgreSQL does *not* allow data loss if it's physically possible to prevent it.
Seems like we're trying to protect users from themselves again. This is not a PostgreSQL database issue; it's a feature designed for application developers and cases where there is the possibility of acceptable data loss for certain types of operations or transactions. We already have the capacity for loss when fsync is disabled; this is just a more controlled feature. Under Oracle, NOWAIT is an asynchronous commit... anyone that uses it should understand that it's still not on-disk and that they can lose it in the event of a failure. That's what Oracle's docs even say. It's just a risk vs. reward trade off. -- Jonah H. Harris, Software Architect | phone: 732.331.1324 EnterpriseDB Corporation | fax: 732.331.1301 33 Wood Ave S, 3rd Floor | [EMAIL PROTECTED] Iselin, New Jersey 08830 | http://www.enterprisedb.com/ ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
