Dead link in release notes for 19
Hi,
in the release notes for 19 there is a dead link in section "E.1.3.2. Query Commands", first entry, first link:
Regards
Daniel
On Mon, 2026-04-27 at 05:36 +0000, Daniel Westermann (DWE) wrote:
in the release notes for 19 there is a dead link in section "E.1.3.2. Query Commands", first entry, first link:
Strange, the link works for me.
It points to commit 2f094e7ac691abc9d2fe0f4dcf0feac4a6ce1d9c.
Yours,
Laurenz Albe
Strange, the link works for me.
It points to commit 2f094e7ac691abc9d2fe0f4dcf0feac4a6ce1d9c.
Yes, now it works. This morning it gave some XML error.
Regards
Daniel
On 4/27/26 3:55 AM, Daniel Westermann (DWE) wrote:
Strange, the link works for me.
It points to commit 2f094e7ac691abc9d2fe0f4dcf0feac4a6ce1d9c.Yes, now it works. This morning it gave some XML error.
When I clicked the link, the page errors, but there's an error message
at the top:
===
This page contains the following errors:
error on line 6484 at column 177: EntityRef: expecting ';'
Below is a rendering of the page up to the first error.
===
I think this may be an issue with gitweb?
Jonathan
On 4/27/26 3:55 AM, Daniel Westermann (DWE) wrote:
Strange, the link works for me.
It points to commit 2f094e7ac691abc9d2fe0f4dcf0feac4a6ce1d9c.Yes, now it works. This morning it gave some XML error.
When I clicked the link, the page errors, but there's an error message
at the top:
===
This page contains the following errors:
error on line 6484 at column 177: EntityRef: expecting ';'
Below is a rendering of the page up to the first error.
===
I think this may be an issue with gitweb?
Now it is back to not working, and this is what I get:
XML Parsing Error: unclosed token
Location: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=2f094e7ac
Line Number 5231, Column 41:
<div class="diff ctx"> &nb
----------------------------------------^
Regards
Daniel
Jonathan
"Jonathan S. Katz" <jkatz@postgresql.org> writes:
On 4/27/26 3:55 AM, Daniel Westermann (DWE) wrote:
Strange, the link works for me.
It points to commit 2f094e7ac691abc9d2fe0f4dcf0feac4a6ce1d9c.
Yes, now it works. This morning it gave some XML error.
When I clicked the link, the page errors, but there's an error message
at the top:
===
This page contains the following errors:
error on line 6484 at column 177: EntityRef: expecting ';'
Below is a rendering of the page up to the first error.
===
I think this may be an issue with gitweb?
Yeah, I got a rendering error too (yet a different one). I think that
commit is so large that we're running into browser rendering engine
bugs. Or maybe gitweb is failing to send it all.
regards, tom lane
On Mon, 27 Apr 2026 at 16:37, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Jonathan S. Katz" <jkatz@postgresql.org> writes:
On 4/27/26 3:55 AM, Daniel Westermann (DWE) wrote:
Strange, the link works for me.
It points to commit 2f094e7ac691abc9d2fe0f4dcf0feac4a6ce1d9c.Yes, now it works. This morning it gave some XML error.
When I clicked the link, the page errors, but there's an error message
at the top:===
This page contains the following errors:
error on line 6484 at column 177: EntityRef: expecting ';'
Below is a rendering of the page up to the first error.
===I think this may be an issue with gitweb?
Yeah, I got a rendering error too (yet a different one). I think that
commit is so large that we're running into browser rendering engine
bugs. Or maybe gitweb is failing to send it all.
It's working right now, but next time it fails, if someone can check with a
view source or similar if it happens to be that gitweb just cut off the
outputsomewhere in th emiddle without finishing it. That is, if it is a
HTML page but doesn't go all the way to </html>.
//Magnus
Hi Magnus,
Yeah, I got a rendering error too (yet a different one). I think that
commit is so large that we're running into browser rendering engine
bugs. Or maybe gitweb is failing to send it all.
It's working right now, but next time it fails, if someone can check with a view source or similar if it happens to be that >gitweb just cut off the outputsomewhere in th emiddle without finishing it. That is, if it is a HTML page but doesn't go all >the way to </html>.
... this is how the page ends when it is not working (Browser is Firefox):
<div class="patch" id="patch90">
<div class="diff header">diff --git <a class="path" href="/gitweb/?p=postgresql.git;a=blob;f=src/include/parser/analyze.h;h=abc5f11cafd6655c57e77f4cac7522ad6a1ed4b1">a/src/include/parser/analyze.h</a> <a class="path" href="/gitweb/?p=postgresql.git;a=blob;f=src/include/parser/analyze.h;h=e10270ff0ffdedc9cc1e713c5b1431558cc594ca;hb=2f094e7ac">b/src/include/parser/analyze.h</a></div>
<div class="diff extended_header">
index abc5f11cafd6655c57e77f4cac7522ad6a1ed4b1..e10270ff0ffdedc9cc1e713c5b1431558cc594ca 100644<span class="info"> (file)</span><br/>
</div>
<div class="diff from_file">--- a/<a class="path" href="/gitweb/?p=postgresq
Regards
Daniel