From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | michael(at)paquier(dot)xyz |
Cc: | exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot |
Date: | 2023-04-28 06:06:28 |
Message-ID: | 20230428.150628.727832009396744479.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
At Fri, 28 Apr 2023 15:04:04 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> At Fri, 28 Apr 2023 13:37:23 +0900, Michael Paquier <michael(at)paquier(dot)xyz> wrote in
> > FWIW, I was looking at this patch and this proposal of relying on a
> > static flag to conditionally clear a snapshot looks rather brittle by
> > design to me because this relies on quite a few assumptions that the
> > snapshot will always be cleared when necessary, as proved by the two
> > code paths of pgstat.c patched where each gain a check on
>
> pgstat_get_stat_snapshot_timestmp() necessarily requires that. Just
Sorry, this is actually the opposite.
pgstat_get_stat_snapshot_timestmp() doesn't necessarily requires that. Just
> for seeming consistency. The only significant part is
> gstat_prep_snapshot, which is always called when the caller wants a
> snapshot.
Regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2023-04-28 06:21:49 | Re: BUG #17903: There is a bug in the KeepLogSeg() |
Previous Message | Kyotaro Horiguchi | 2023-04-28 06:04:04 | Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot |