Search Postgresql Archives

Re: Unlogged Crash Detection

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I see, interesting.

We have lots of unlogged tables, upon a crash we want to create a feedback/alert that data disappeared.

Not very familiar with the internal structure, but is it possible to identify if the current table is the INIT_FORKNUM?

Gersner

On Tue, Aug 29, 2017 at 11:27 AM, Michael Paquier <michael.paquier@xxxxxxxxx> wrote:
On Tue, Aug 29, 2017 at 5:17 PM, Gersner <gersner@xxxxxxxxx> wrote:
> Is there a reliable way to distinguish between an empty unlogged table to an
> unlogged table which has been truncated due to a crash?

Why do you want to make such a difference? At the beginning of a crash
recovery all the, the existing relation files of unlogged tables are
all removed, and replaced by the init forknum which represents their
initial state. You can see by yourself ResetUnloggedRelations &
friends in reinit.c.
--
Michael


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux