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: Fri, 15 Apr 2022 12:40:39 -0400
Message-ID: <1650836.1650040839@sss.pgh.pa.us> (raw)
In-Reply-To: <CAH2-Wzm-rZnt5fpgsaAngCDj+Gy6O4_Vxp9msQ_oD6UOLcqPpQ@mail.gmail.com>
References: <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>
	<20220415015249.kfsqxujrf2bn2wz6@alap3.anarazel.de>
	<20220415024515.GA862547@rfd.leadboat.com>
	<20220415051205.6abhlilh6fnjgohr@alap3.anarazel.de>
	<20220415052125.GD862547@rfd.leadboat.com>
	<1637671.1650032132@sss.pgh.pa.us>
	<1643035.1650035653@sss.pgh.pa.us>
	<CAH2-Wzm-rZnt5fpgsaAngCDj+Gy6O4_Vxp9msQ_oD6UOLcqPpQ@mail.gmail.com>

Peter Geoghegan <pg@bowt.ie> writes:
> On Fri, Apr 15, 2022 at 8:14 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> BTW, before I forget: the wording of this log message is just awful.
>> [ so how about ]
>> "removable cutoff: %u, which was %d xids old when operation ended\n"

> How the output appears when placed right before the output describing
> how VACUUM advanced relfrozenxid is an important consideration. I want
> the format and wording that we use to imply a relationship between
> these two things. Right now, that other line looks like this:

> "new relfrozenxid: %u, which is %d xids ahead of previous value\n"

> Do you think that this juxtaposition works well?

Seems all right to me; do you have a better suggestion?

			regards, tom lane





view thread (88+ messages)  latest in thread

Message-ID: <1650836.1650040839@sss.pgh.pa.us>
Permalink:  ../1650836.1650040839@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1650836.1650040839@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: <1650836.1650040839@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