Re: Intermittent buildfarm failures on wrasse
От | Peter Geoghegan |
---|---|
Тема | Re: Intermittent buildfarm failures on wrasse |
Дата | |
Msg-id | CAH2-Wzm-rZnt5fpgsaAngCDj+Gy6O4_Vxp9msQ_oD6UOLcqPpQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Intermittent buildfarm failures on wrasse (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Intermittent buildfarm failures on wrasse
Re: Intermittent buildfarm failures on wrasse |
Список | pgsql-hackers |
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. > On first sight, I thought that it meant that we'd computed OldestXmin > a second time and discovered that it advanced by 26 xids while the VACUUM > was running. > "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? > Also, is it really our practice to spell XID in lower-case in > user-facing messages? There are examples of both. This could easily be changed to "XIDs". -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: