From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: xmlserialize bug - extra empty row at the end |
Date: | 2023-04-23 16:03:00 |
Message-ID: | CAMsGm5f1z0A7G3edJTQB5iDzT2pHVx_NiGGz9GZju9pXx412xQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 23 Apr 2023 at 10:52, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Isaac Morland <isaac(dot)morland(at)gmail(dot)com> writes:
>
> > I might go so
> > far as to change the psql display routines to not leave a blank line
> after
> > the content in the event it ends with a newline.
>
> psql has *no* business changing what it displays: if what came from the
> server has a trailing newline, that had better be made visible. Even if
> we thought it was a good idea, it's about 25 years too late to reconsider
> that. However, xmlserialize()'s new indenting behavior isn't set in
> stone yet, so we could contemplate chomping newlines within that.
The trailing newline is made visible by the little bent arrow character
that appears at the right hand side. So you could still tell whether the
value ended with a trailing newline. I agree that simply dropping the
trailing newline before displaying the value would be a very bad idea.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2023-04-23 16:28:35 | Re: xmlserialize bug - extra empty row at the end |
Previous Message | Jelte Fennema | 2023-04-23 15:29:15 | Re: run pgindent on a regular basis / scripted manner |