* Anibal David Acosta (aa@devshock.com) wrote:
> Unlogged tables are not memory tables don't?
Unlogged tables are not memory tables.
> If we stop postgres server (normal stop) and start again, all information in
> unlogged tables still remain?
Yes.
> So, can I expect a data loss just in case of crash, power failure or SO
> crash don't?
Yes.
> In case of crash, is possible that data corruption happened in a unlogged
> tables?
In a crash, unlogged tables are automatically truncated.
> For performance purpose can I use async commit and unlogged tables?
I'm not aware of any issues (beyond those already documented for async
commit..) with having async commit and unlogged tables.
THanks,
Stephen
