| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Anibal David Acosta <aa(at)devshock(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: unlogged tables |
| Date: | 2011-11-11 20:18:22 |
| Message-ID: | 20111111201822.GN24234@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
* Anibal David Acosta (aa(at)devshock(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shaun Thomas | 2011-11-11 22:21:18 | Using incrond for archiving |
| Previous Message | Anibal David Acosta | 2011-11-11 20:08:44 | unlogged tables |