Re: improving wraparound behavior

Hi,

On 2019-05-03 23:08:44 -0400, Stephen Frost wrote:
> This makes me think we should both order it and combine it into one
> message... but that'd then be pretty difficult to deal with,
> potentially, from a translation standpoint and just from a "wow, that's
> a huge log message", which is kind of the idea behind the SRF- to give
> you all that info in a more easily digestible manner.
>
> Not sure I've got any great ideas on how to improve on this. I do think
> that if we know that there's multiple different things that are within a
> small number of xids of the oldest xmin then we should notify the user
> about all of them, either directly in the error messages or by referring
> them to the SRF, so they have the opportunity to address them all, or
> at least know about them all. As mentioned though, it's likely to be a
> quite rare thing to run into, so you'd have to be extra unlucky to even
> hit this case and perhaps the extra code complication just isn't worth
> it.

I think just having an actual reason for the problem would be so much
better than the current status, that I'd tackle the "oops, just about
everything is screwed, here's the reasons in order" case separately (or
just plain never).

Greetings,

Andres Freund