Re: Make description of heap records more talkative for flags

From: Andres Freund <andres(at)anarazel(dot)de>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
Subject: Re: Make description of heap records more talkative for flags
Date: 2018-05-15 17:50:25
Message-ID: 20180515175025.tmoo6tuzwa3lpriw@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018-05-15 13:44:58 -0400, Alvaro Herrera wrote:
> On 2018-Apr-23, Alvaro Herrera wrote:
>
> > Now, frankly, this being mostly a debugging tool, I think it would be
> > better to have the output as complete as we can. Otherwise, when
> > debugging some hideous problem we find ourselves patching the tool
> > during an emergency in order to figure out what is going on. For this,
> > I would rather patch the earliest version we conveniently can. We
> > cannot patch pg10 because it's already out there, but not so for pg11.
>
> RMT, I would like your opinion on whether to apply a fix for this
> problem to pg11 or not.

-0.1. We've lived without this for years, I fail to see why this should
get an exception / has any sort of urgency. We could establish a policy
that we just exclude parts of the source tree from the code freeze, but
we haven't so far.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2018-05-15 18:47:26 Re: Postgres 11 release notes
Previous Message Daniel Verite 2018-05-15 17:45:27 Re: Allow COPY's 'text' format to output a header