| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| 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 09:25:25 |
| Message-ID: | CA+OCxoyfgTUE4JYp+D3=r+Nr9hwJeZxRCQC69GVDA6KLJfm3qA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 8 Nov 2022 at 04:10, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> 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.
>
Thank you!
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2022-11-08 09:36:17 | Re: Reviving lost replication slots |
| Previous Message | Andy Fan | 2022-11-08 09:04:00 | Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not? |