| From: | Frits Jalvingh <jal(at)etc(dot)to> |
|---|---|
| To: | daniel(at)yesql(dot)se |
| Cc: | 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 11:38:38 |
| Message-ID: | CAKhTGFUG-68+QhbdZeGM7XFh+S55GfjGX+iH32z8rpLsr+sHCw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thanks a lot for fixing it!
On Fri, Oct 23, 2020 at 1:12 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> > 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).
>
> cheers ./daniel
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-10-23 15:20:12 | Re: BUG #16683: explain plan format xml produces invalid xml |
| Previous Message | Daniel Gustafsson | 2020-10-23 11:12:13 | Re: BUG #16683: explain plan format xml produces invalid xml |