Re: Detailed release notes

From: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Detailed release notes
Date: 2024-08-05 11:16:23
Message-ID: CAB-JLwbErUkZqcOXpf6vAy7EUBMgiHC3xB5oKdSOqjOMar8_Vw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em seg., 5 de ago. de 2024 às 07:54, jian he <jian(dot)universality(at)gmail(dot)com>
escreveu:

>
> [commitId_link1, commitId_link2]: Change functions to use a safe
> search_path during maintenance operations (Jeff Davis)
>

I don't like that prefix dirtying each item.
I think having just a link after every item would be better.
Firstly because in English we read left to right and
also because we don't need the commit code. So it would be

- Change functions to use a safe search_path during maintenance
operations (Jeff Davis) [link1, link2]

or just a number to it

- Change functions to use a safe search_path during maintenance
operations (Jeff Davis) [1, 2]

regards
Marcos

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2024-08-05 11:26:23 Re: Speed up JSON escape processing with SIMD plus other optimisations
Previous Message Michail Nikolaev 2024-08-05 11:11:50 Re: [BUG?] check_exclusion_or_unique_constraint false negative