pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Andres Freund <andres@anarazel.de>
Cc: Noah Misch <noah@leadboat.com>
Cc: David Rowley <dgrowleyml@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Intermittent buildfarm failures on wrasse
Date: Thu, 14 Apr 2022 22:20:29 -0400
Message-ID: <1574961.1649989229@sss.pgh.pa.us> (raw)
In-Reply-To: <CAH2-WznEA4EYSdtPTaj_sTpSBvw8EtzxnFAEtEXQK2MYyCNq6A@mail.gmail.com>
References: <1364997.1649893086@sss.pgh.pa.us>
	<CAH2-WzkUGqFNXhnFRbVG4xfTo3WpapcdRaH4hQSTrNvDgYvYoQ@mail.gmail.com>
	<1365924.1649893883@sss.pgh.pa.us>
	<CAH2-Wzn2Obp90oyZa5HN26rzG8ozzHM3dgkpLcsVzxTR+jK5NQ@mail.gmail.com>
	<1374062.1649896550@sss.pgh.pa.us>
	<20220414010505.s7z24jxrfsjbzz7l@alap3.anarazel.de>
	<1401379.1649899392@sss.pgh.pa.us>
	<20220414015112.yhruzx3dbjnz4pji@alap3.anarazel.de>
	<20220414025122.GA808845@rfd.leadboat.com>
	<1486022.1649952083@sss.pgh.pa.us>
	<20220414161850.ibqkevxcv6a7vdxg@alap3.anarazel.de>
	<1521388.1649953580@sss.pgh.pa.us>
	<1547912.1649971995@sss.pgh.pa.us>
	<CAH2-Wz=DHY2LV7=2aVd=qz6AbQhFK7KJRNL5ZwgB7dyno_gzdg@mail.gmail.com>
	<1553951.1649975018@sss.pgh.pa.us>
	<CAH2-WzngTjUk_65ESmrMf40WTqasrmWG0gpwnvcN+mXsoXT7qQ@mail.gmail.com>
	<CAH2-WznXXkkfE_y9ieaHkEQj31HeMAqJBtJPmDY+EpyVg1QywQ@mail.gmail.com>
	<1570894.1649986347@sss.pgh.pa.us>
	<CAH2-WznQ2j3n9QwfJ5Cp6RAPfbYCkh-Bgj2Vyk6Qh_HwFULRYw@mail.gmail.com>
	<1572437.1649987614@sss.pgh.pa.us>
	<CAH2-WznEA4EY! SdtPTaj_sTpSBvw8EtzxnFAEtEXQK2MYyCNq6A@mail.gmail.com>

Peter Geoghegan <pg@bowt.ie> writes:
> That was the intent, but that in itself doesn't mean that it isn't
> something to do with setting hint bits (not the OldestXmin horizon
> being held back).

Oh!  You mean that maybe the OldestXmin horizon was fine, but something
decided not to update hint bits (and therefore also not the all-visible
bit) anyway?  Worth investigating I guess.

> I'd really like to know what the removable cutoff
> looks like for these VACUUM operations, which is something like
> Andres' VACUUM VERBOSE debug patch should tell us.

Yeah.  I'd hoped to investigate this manually and not have to clutter
the main repo with debugging commits.  However, since I've still
utterly failed to reproduce the problem on wrasse's host, I think
we're going to be forced to do that.

			regards, tom lane





view thread (88+ messages)  latest in thread

Message-ID: <1574961.1649989229@sss.pgh.pa.us>
Permalink:  ../1574961.1649989229@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1574961.1649989229@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pg@bowt.ie, andres@anarazel.de, noah@leadboat.com, dgrowleyml@gmail.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: Intermittent buildfarm failures on wrasse
  In-Reply-To: <1574961.1649989229@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox