Re: Unlogged tables, persistent kind - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Unlogged tables, persistent kind
Date
Msg-id 17903.1303680470@sss.pgh.pa.us
Whole thread Raw
In response to Unlogged tables, persistent kind  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Unlogged tables, persistent kind  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> If you don't log changes to tables you have two choices if we crash
> 1) truncate the table and any indexes
> 2) rebuild any indexes damaged by the crash

No, you have only one choice, and that's (1), because there's no
guarantee that what's in the table file is meaningful.

> Heap blocks would be zeroed if they were found to be damaged, following a crash.

This is sheerest fantasy.  And even if you could implement it, what sort
of feature would you be offering?  "Your data is preserved except when
it isn't"?  People who want that can go use mysql.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: windows consolidated cleanup
Next
From: Tom Lane
Date:
Subject: Re: operator classes for index?