Re: Make unlogged table resets detectable

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Make unlogged table resets detectable
Date: 2021-06-08 03:46:05
Message-ID: YL7n/RffStYrmxX0@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 07, 2021 at 02:56:57PM -0400, Tom Lane wrote:
> +1. I'd support recording the time of the last crash recovery, as
> well as having a counter. I think an LSN would not be as useful
> as a timestamp.

One could guess a timestamp based on a LSN, no? So I'd like to think
the opposite actually: a LSN would be more useful than a timestamp.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2021-06-08 04:16:48 Re: Hook for extensible parsing.
Previous Message Amit Kapila 2021-06-08 03:33:45 Re: [bug?] Missed parallel safety checks, and wrong parallel safety