From: | jian he <jian(dot)universality(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Detailed release notes |
Date: | 2024-08-05 10:54:10 |
Message-ID: | CACJufxFFvo09kd1bCR0VuQoiyhj44hM6JSWzAvPFHMVMmXT+Xg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jul 26, 2024 at 10:11 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
> >> On 26 Jul 2024, at 15:00, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> wrote:
> >> But why is that just a hidden comment and not a visible link for us ?
>
> > That's likely the wrong level of detail for the overwhelming majority of
> > release notes readers. I have a feeling this was discussed not too long ago
> > but (if so) I fail to find that discussion now.
>
> Yeah, I too recall some discussion of surfacing the commit links
> somehow, perhaps as a popup tooltip. Nobody's got round to it yet.
> It's not real clear how to handle multiple links per <para>, which
> happens from time to time in major release notes and just about
> everyplace in minor release notes.
>
similar to https://docs.python.org/3/whatsnew/changelog.html
Change functions to use a safe search_path during maintenance
operations (Jeff Davis)
change to
[commitId_link1, commitId_link2]: Change functions to use a safe
search_path during maintenance operations (Jeff Davis)
Does this make sense?
If so, then we can hardcode and some automation can change to that way.
From | Date | Subject | |
---|---|---|---|
Next Message | Michail Nikolaev | 2024-08-05 11:11:50 | Re: [BUG?] check_exclusion_or_unique_constraint false negative |
Previous Message | Amit Kapila | 2024-08-05 10:52:20 | Re: Conflict detection and logging in logical replication |