Re: Tracking last scan time

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Robert Treat <rob(at)xzilla(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Vik Fearing <vik(at)postgresfriends(dot)org>
Subject: Re: Tracking last scan time
Date: 2022-11-08 04:09:59
Message-ID: Y2nWl/bFyEEogfc5@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 07, 2022 at 04:54:07PM +0900, Michael Paquier wrote:
> FWIW, all the other areas of pgstatfuncs.c manipulate timestamptz
> fields with a style like the attached. That's a nit, still per the
> role of consistency with the surroundings..
>
> Anyway, it seems to me that a regression test is in order before a
> scan happens just after the relation creation, and the same problem
> shows up with last_idx_scan.

Hearing nothing, done this way as of d7744d5. Thanks for the report,
Robert. And thanks for the patch, Dave.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Takamichi Osumi (Fujitsu) 2022-11-08 04:12:00 RE: Data is copied twice when specifying both child and parent table in publication
Previous Message Michael Paquier 2022-11-08 04:07:57 Re: Use pg_pwritev_with_retry() instead of write() in dir_open_for_write() to avoid partial writes?