From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com> |
Subject: | Re: Inconsistency in determining the timestamp of the db statfile. |
Date: | 2020-09-09 16:01:26 |
Message-ID: | 20200909160126.GA24248@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2020-Sep-09, Amit Kapila wrote:
> I have included Alvaro as he is a committer for 187492b6, so he might
> remember something and let us know if this is a mistake or there is
> some reason for doing so (return true even when the db entry we are
> trying to read is corrupt).
Thanks -- I have to excuse myself here, as I don't have too many
memories about this. It seems y'all have derived more insight that I
could possibly offer.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | John Naylor | 2020-09-09 16:04:28 | Re: WIP: BRIN multi-range indexes |
Previous Message | Heikki Linnakangas | 2020-09-09 15:39:41 | Re: Yet another fast GiST build |