Tom Lane [mailto:[EMAIL PROTECTED] That should be user-scriptable policy, in my worldview.
O... and other dbms will freeze when this situation is hit, rather than continue and drop archive logs.]
Been there, done that, don't see how it's any better. I hesitate to be
real specific here, but let's just say the end result was restore from backup :-(
So, if we had a parameter called Wal_archive_policy that has 3 settings: None = no archiving Optimistic = archive, but if for some reason log space runs out then make space by dropping the oldest archive logs Strict = if log space runs out, stop further write transactions from committing, by whatever means, even if this takes down dbms.
That sounds good to me. For the "Optimistic" case, we need to yell loudly if we do find ourselves needing to drop segments. For the "Strict" case, we just need to be sure it works correctly ;-)
Joe
---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
