Re: BUG #16683: explain plan format xml produces invalid xml

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: jal(at)etc(dot)to, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Subject: Re: BUG #16683: explain plan format xml produces invalid xml
Date: 2020-10-23 15:20:12
Message-ID: 156587.1603466412@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>> On 23 Oct 2020, at 12:26, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
>> Sort-Space is incorrectly finished with /Sort-Spaces

> Nice catch, it was introduced in the Incremental Sort patch, both for disk and
> memory type sorts as per the attached (unless the opening of the group was
> supposed to be "Sort Spaces" but singular seems the right choice here).

Agreed. Will push in a bit.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Langote 2020-10-23 15:36:56 Re: BUG #16644: null value for defaults in OLD variable for trigger
Previous Message Frits Jalvingh 2020-10-23 11:38:38 Re: BUG #16683: explain plan format xml produces invalid xml