Re: Unlogged Crash Detection

From: Gersner <gersner(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: Unlogged Crash Detection
Date: 2017-08-29 09:06:33
Message-ID: CALKrh6nmW+Hde=mRCBZ6_6W9C8wZ=dgb1WqHGA+ONCeD7igA9g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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(dot)paquier(at)gmail(dot)com
> wrote:

> On Tue, Aug 29, 2017 at 5:17 PM, Gersner <gersner(at)gmail(dot)com> 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
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paquier 2017-08-29 11:19:52 Re: Unlogged Crash Detection
Previous Message Michael Paquier 2017-08-29 08:27:49 Re: Unlogged Crash Detection