"Tom Lane" <[EMAIL PROTECTED]> writes: >> If we don't do that then regular users have the ability to put the >> catalog (and by extension everything else) at risk... > > How do you arrive at that conclusion? The point of the async commit > patch is that transactions might be lost, as in not really committed, > but there can be no database corruption. Otherwise we'd never consider > making it a userset config setting.
I think the danger that arises is not related to catalogs so much as it is related to end-of-transaction filesystem operations such as dropping heap files. If those operations are done but the related transaction commit is lost then you have a problem. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
