On Mon, Jul 29, 2019 at 10:56 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Michael Paquier <michael@paquier.xyz> writes:
> > On Fri, Jul 26, 2019 at 08:24:16PM -0400, Tom Lane wrote:
> >> I think this is a sufficiently obvious bug, and a sufficiently
> >> obvious fix, that we should just fix it and not insist on getting
> >> a reproducible test case first. I think a test case would soon
> >> bit-rot anyway, and no longer exercise the problem.
> >> I certainly do *not* want to wait so long that we miss the
> >> upcoming minor releases.
>
> > +1. Any volunteers?
>
> If Robert doesn't weigh in pretty soon, I'll take responsibility for it.
That's fine, or if you prefer that I commit it, I will.
I just got back from a week's vacation and am only very gradually
unburying myself from mounds of email. (Of course, the way
pgsql-hackers is getting, there's sort of always a mound of email
these days.)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company