Re: list of acknowledgments for PG16

Hi, > On Aug 22, 2023, at 17:33, Peter Eisentraut wrote: > > The list of acknowledgments for the PG16 release notes has been committed. > It should show up here sometime: > . > As usual, please check for problem

Re: list of acknowledgments for PG16

On 16.10.23 15:46, Alvaro Herrera wrote: On 2023-Aug-27, Peter Eisentraut wrote: On 22.08.23 15:48, Vik Fearing wrote: I think these might be the same person:     Zhihong Yu     Zihong Yu I did not spot any others. Fixed. Hm, I noticed we also list Ted Yu, but that's the same perso

Re: list of acknowledgments for PG16

On 2023-Aug-27, Peter Eisentraut wrote: > On 22.08.23 15:48, Vik Fearing wrote: > > I think these might be the same person: > > > >     Zhihong Yu > >     Zihong Yu > > > > I did not spot any others. > > Fixed. Hm, I noticed we also list Ted Yu, but that's the same person as Zhihong Yu. --

Re: list of acknowledgments for PG16

On 8/22/23 16:24, Peter Eisentraut wrote: On 22.08.23 15:29, Tom Lane wrote: Alvaro Herrera writes: Yeah, I've been proposing this kind of thing for many years; the problem, until not long ago, was that the tooling was unable to process non-Latin1 characters in all the output formats that we u

Re: list of acknowledgments for PG16

I'm not completely sure what should be in this list, but maybe also tuplesort extensibility [1]? [1] https://www.postgresql.org/message-id/flat/CALT9ZEHjgO_r2cFr35%3Du9xZa6Ji2e7oVfSEBRBj0Gc%2BtJjTxSg%40mail.gmail.com#201dc4202af38f224a1e3acc78795199

Re: list of acknowledgments for PG16

On 23.08.23 09:13, Denis Laxalde wrote: Peter Eisentraut a écrit : The list of acknowledgments for the PG16 release notes has been committed.  It should show up here sometime: .    As usual, please check for problems

Re: list of acknowledgments for PG16

On 22.08.23 15:48, Vik Fearing wrote: On 8/22/23 11:33, Peter Eisentraut wrote: The list of acknowledgments for the PG16 release notes has been committed.  It should show up here sometime: .  As usual, please check

Re: list of acknowledgments for PG16

> On 25 Aug 2023, at 14:22, Magnus Hagander wrote: > On Tue, Aug 22, 2023 at 4:03 PM Joe Conway wrote: >> I'm sure we could figure out how to just release the updated docs, but >> with RC1 a week away, is it really worthwhile? > > We've also been pretty strict to say that we don't *want* unrele

Re: list of acknowledgments for PG16

On Tue, Aug 22, 2023 at 4:03 PM Joe Conway wrote: > > On 8/22/23 09:44, Tom Lane wrote: > > Alvaro Herrera writes: > >> On 2023-Aug-22, Peter Eisentraut wrote: > >>> The list of acknowledgments for the PG16 release notes has been committed. > >>> It should show up here sometime: > >>>

Re: list of acknowledgments for PG16

On Tue, Aug 22, 2023 at 9:41 PM Vik Fearing wrote: > > > I am struggling to find documentation on how to build the pdfs with > meson. Any pointers? > -- > Vik Fearing > > > ninja docs: https://wiki.postgresql.org/wiki/Meson#Meson_documentation ninja alldocs. which take some time, build all kind

Re: list of acknowledgments for PG16

On Tue, Aug 22, 2023 at 6:33 PM Peter Eisentraut wrote: > As usual, please check for problems such as wrong sorting, duplicate > names in different variants, or names in the wrong order etc. (Our > convention is given name followed by surname.) I went through Japanese names on the list. I thi

Re: list of acknowledgments for PG16

Peter Eisentraut a écrit : The list of acknowledgments for the PG16 release notes has been committed. It should show up here sometime: . As usual, please check for problems such as wrong sorting, duplicate names i

Re: list of acknowledgments for PG16

On Tue, Aug 22, 2023 at 10:03:29AM -0400, Joe Conway wrote: > On 8/22/23 09:44, Tom Lane wrote: > > Alvaro Herrera writes: > > > On 2023-Aug-22, Peter Eisentraut wrote: > > > > The list of acknowledgments for the PG16 release notes has been > > > > committed. > > > > It should show up here someti

Re: list of acknowledgments for PG16

On 22.08.23 15:29, Tom Lane wrote: Alvaro Herrera writes: Yeah, I've been proposing this kind of thing for many years; the problem, until not long ago, was that the tooling was unable to process non-Latin1 characters in all the output formats that we use. But tooling has changed and the oldest

Re: list of acknowledgments for PG16

On 8/22/23 09:44, Tom Lane wrote: Alvaro Herrera writes: On 2023-Aug-22, Peter Eisentraut wrote: The list of acknowledgments for the PG16 release notes has been committed. It should show up here sometime: . Hmm

Re: list of acknowledgments for PG16

On 8/22/23 11:33, Peter Eisentraut wrote: The list of acknowledgments for the PG16 release notes has been committed.  It should show up here sometime: .  As usual, please check for problems such as wrong sorting, dup

Re: list of acknowledgments for PG16

Alvaro Herrera writes: > On 2023-Aug-22, Peter Eisentraut wrote: >> The list of acknowledgments for the PG16 release notes has been committed. >> It should show up here sometime: >> . > Hmm, I think these docs would

Re: list of acknowledgments for PG16

On 8/22/23 15:29, Tom Lane wrote: Alvaro Herrera writes: Yeah, I've been proposing this kind of thing for many years; the problem, until not long ago, was that the tooling was unable to process non-Latin1 characters in all the output formats that we use. But tooling has changed and the oldest

Re: list of acknowledgments for PG16

Alvaro Herrera writes: > Yeah, I've been proposing this kind of thing for many years; the > problem, until not long ago, was that the tooling was unable to process > non-Latin1 characters in all the output formats that we use. But > tooling has changed and the oldest platforms have disappeared, s

Re: list of acknowledgments for PG16

On 2023-Aug-22, Vik Fearing wrote: > On 8/22/23 11:33, Peter Eisentraut wrote: > > As usual, please check for problems such as wrong sorting, duplicate > > names in different variants, or names in the wrong order etc.  (Our > > convention is given name followed by surname.) > > Not necessarily fo

Re: list of acknowledgments for PG16

On 8/22/23 11:33, Peter Eisentraut wrote: As usual, please check for problems such as wrong sorting, duplicate names in different variants, or names in the wrong order etc.  (Our convention is given name followed by surname.) Not necessarily for this time around, but I would like to see this

Re: list of acknowledgments for PG16

On 2023-Aug-22, Peter Eisentraut wrote: > The list of acknowledgments for the PG16 release notes has been committed. > It should show up here sometime: > . > As usual, please check for problems such as wrong sorting,