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-07 07:54:07
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Thu, Nov 03, 2022 at 04:44:16PM -0400, Dave Page wrote:
> Here's a patch to fix this issue. Many thanks to Peter Eisentraut who
> figured it out in a few minutes after I spent far too long looking down
> rabbit holes in entirely the wrong place.

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.

Attachment Content-Type Size
fix_no_scan_handling_2.diff text/plain 1.8 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2022-11-07 07:58:13 Re: Allow single table VACUUM in transaction block
Previous Message Alexander Pyhalov 2022-11-07 07:52:43 Re: Add semi-join pushdown to postgres_fdw