Re: vacuum verbose detail logs are unclear; log at *start* of each stage

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: vacuum verbose detail logs are unclear; log at *start* of each stage
Date: 2020-07-05 20:48:42
Message-ID: 72121E60-FF4B-42CE-BCB1-E3AE5169F139@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 24 Mar 2020, at 22:58, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> The really fundamental problem with this is that you are trying to make
> the server do what is properly the client's job, namely format messages
> nicely. Please read the message style guidelines [1], particularly
> the bit about "Formatting", which basically says "don't":

This thread has stalled since the last CF with Tom's raised issue unanswered,
and the patch no longer applies. I'm closing this as Returned with Feedback,
if there is an updated patchset then please re-open the entry.

cheers ./daniel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Isaac Morland 2020-07-05 20:53:49 Can I use extern "C" in an extension so I can use C++?
Previous Message Daniel Gustafsson 2020-07-05 20:40:16 Re: Binary support for pgoutput plugin