Re: MultiXact member wraparound protections are now enabled - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: MultiXact member wraparound protections are now enabled
Date
Msg-id CANP8+j+=90dQEx6SJB0hW7OmgMGQVf7V06wucPug7Eor1HHTjg@mail.gmail.com
Whole thread Raw
In response to Re: MultiXact member wraparound protections are now enabled  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: MultiXact member wraparound protections are now enabled  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 22 July 2015 at 21:45, Robert Haas <robertmhaas@gmail.com> wrote:
 
But it seemed to me that this could be rather confusing.  I thought it
would be better to be explicit about whether the protections are
enabled in all cases.  That way, (1) if you see the message saying
they are enabled, they are enabled; (2) if you see the message saying
they are disabled, they are disabled; and (3) if you see neither
message, your version does not have those protections.

(3) would imply that we can't ever remove the message, in case people think they are unprotected.

If we display (1) and then we find a further bug, where does that leave us? Do we put a second "really, really fixed" message?

AIUI this refers to a bug fix, its not like we've invented some anti-virus mode to actively prevent or even scan for further error. I'm not sure why we need a message to say a bug fix has been applied; that is what the release notes are for.

If something is disabled, we should say so, but otherwise silence means safety and success.

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: PL/pgSQL, RAISE and error context
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: multiple psql option -c