someone else to do the list of acknowledgments

The whole thing might take about 20 to 30 hours wall-clock time.

After this dev cycle, things with a defined end to them hold a greater
attraction than they did previously.

So, there is some time to think about this. Please discuss here if
you're interested or have questions.

I am interested.

Hi,

The whole thing might take about 20 to 30 hours wall-clock time.

After this dev cycle, things with a defined end to them hold a greater attraction than they did previously.

So, there is some time to think about this. Please discuss here if
you're interested or have questions.

I am interested.

+1

--
Best regards,
Aleksander Alekseev

Hi,

The whole thing might take about 20 to 30 hours wall-clock time.

After this dev cycle, things with a defined end to them hold a greater attraction than they did previously.

So, there is some time to think about this. Please discuss here if
you're interested or have questions.

I am interested.

+1

Sorry, I've just realized that my +1 can be interpreted as both voting
for Corey and as volunteering for making the list of acknowledgments.
To clarify, I meant that I'm interested too :)

--
Best regards,
Aleksander Alekseev

hi.
maybe we should start working on this?

https://www.postgresql.org/developer/roadmap
says 18 will be released in September 2025.

On Sat, Aug 16, 2025 at 11:58 PM jian he <jian.universality@gmail.com>
wrote:

hi.
maybe we should start working on this?

https://www.postgresql.org/developer/roadmap
says 18 will be released in September 2025.

I am.

On Sun, Aug 17, 2025 at 12:40 PM Corey Huinker <corey.huinker@gmail.com> wrote:

On Sat, Aug 16, 2025 at 11:58 PM jian he <jian.universality@gmail.com> wrote:

hi.
maybe we should start working on this?

https://www.postgresql.org/developer/roadmap
says 18 will be released in September 2025.

I am.

hi.
Maybe you can share the draft patch so others can review it.

https://www.postgresql.org says:
"The planned date for the general availability of PostgreSQL 18 is
September 25, 2025."

516 contributors this cycle vs 462 last cycle.

When name accents/capitalization differed, I went with the string used in
the previous year.

Some of the names that come from bug reports and doc fixes are just first
names, and the discussion threads shed no light on the full name of the
person.

I have a git log that has been "redacted", which is to say that every name
attribution has been screened out, as well as names of known past
contributors, and various other name-looking things that aren't people (ex.
Microsoft Windows) screened out. Even with all that automation it is still
over 50k lines, so if you want to double check that, make sure you have a
comfy chair.

On Tue, Sep 9, 2025 at 12:07 PM jian he <jian.universality@gmail.com> wrote:

Em qua., 10 de set. de 2025 às 12:11, Corey Huinker <corey.huinker@gmail.com>
escreveu:

516 contributors this cycle vs 462 last cycle.

When name accents/capitalization differed, I went with the string used in
the previous year.

Some of the names that come from bug reports and doc fixes are just first
names, and the discussion threads shed no light on the full name of the
person.

I have a git log that has been "redacted", which is to say that every name
attribution has been screened out, as well as names of known past
contributors, and various other name-looking things that aren't people (ex.
Microsoft Windows) screened out. Even with all that automation it is still
over 50k lines, so if you want to double check that, make sure you have a
comfy chair.

I think that "Rainier Vilela" is a mistake and should be removed.
The correct is "Ranier Vilela"

best regards,
Ranier Vilela

On 10 Sep 2025, at 17:11, Corey Huinker <corey.huinker@gmail.com> wrote:

516 contributors this cycle vs 462 last cycle.

When name accents/capitalization differed, I went with the string used in the previous year.

Some of the names that come from bug reports and doc fixes are just first names, and the discussion threads shed no light on the full name of the person.

I have a git log that has been "redacted", which is to say that every name attribution has been screened out, as well as names of known past contributors, and various other name-looking things that aren't people (ex. Microsoft Windows) screened out. Even with all that automation it is still over 50k lines, so if you want to double check that, make sure you have a comfy chair.

A few probable, or guaranteed, duplicates:

Daniel Gustafs
Daniel Gustafsson

Kuntal Ghosh
Kuntal Gosh

Yasir
Yasir Hussain

There are a few first-names-only that need to be verified, IME they resolve to
a name already on the list.

Andrew
Dmitry
Felix

--
Daniel Gustafsson

On 2025-Sep-10, Corey Huinker wrote:

Aysén Region

This is not a contributor name but a toponymic. I think you got it from this
commit:

commit 368c3fbf9da96787d4e7cae61e11518d72f75071
Author: Tom Lane <tgl@sss.pgh.pa.us> []
AuthorDate: Wed Apr 30 11:13:49 2025 -0400
CommitDate: Wed Apr 30 11:13:49 2025 -0400

Update time zone data files to tzdata release 2025b.

DST law changes in Chile: there is a new time zone America/Coyhaique
for Chile's Aysén Region, to account for it changing to UTC-03
year-round and thus diverging from America/Santiago.

Historical corrections for Iran.

Backpatch-through: 13

Also please note that my name appears twice, once with A and once with
Á (sorts at the end). The latter is correct.

"Yasir" is the same person as "Yasir Hussain".

"Anton A. Melnikov" is probably the same as "Anton Melnikov", and "David
E. Wheeler" is likely "David Wheeler".

Per /messages/by-id/18806-d70b0c9fdf63dcbf@postgresql.org
we can credit 孟令彬 as "lingbin meng".

Per /messages/by-id/tencent_CA843A8385CB3130B9ABC1E55023FC4E4D05@qq.com
we can credit 清浅 as "Chengwen Wu".

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Hay dos momentos en la vida de un hombre en los que no debería
especular: cuando puede permitírselo y cuando no puede" (Mark Twain)

On Wed, Sep 10, 2025 at 07:57:26PM +0200, Alvaro Herrera wrote:

Per /messages/by-id/tencent_CA843A8385CB3130B9ABC1E55023FC4E4D05@qq.com
we can credit 清浅 as "Chengwen Wu".

Good catch, thanks! I didn't notice his name as this message seems to
have been cut from the original thread where the bug has been
reported.
--
Michael

On Wed, Sep 10, 2025 at 11:11 PM Corey Huinker <corey.huinker@gmail.com> wrote:

516 contributors this cycle vs 462 last cycle.

When name accents/capitalization differed, I went with the string used in the previous year.

Some of the names that come from bug reports and doc fixes are just first names, and the discussion threads shed no light on the full name of the person.

I have a git log that has been "redacted", which is to say that every name attribution has been screened out, as well as names of known past contributors, and various other name-looking things that aren't people (ex. Microsoft Windows) screened out. Even with all that automation it is still over 50k lines, so if you want to double check that, make sure you have a comfy chair.

Andrei Lepikhov
Andrey Lepikhov
refers to the same person, I think.

Masao Fujii
Fujii Masao
refers to the same person too?

Junwang Zhao
Zhao Junwang
refers to the same person too?

"Hacking Discord" wrong?

hi.

Nikita
Nikita Kalinin
Nikita Malakhov
The first "Nikita" refers to the commit below
058b5152f02ef86c98a795c14dbd6a8e195f4fd1.

Author: Daniel Gustafsson <dgustafsson@postgresql.org>
Date: Thu Mar 27 22:57:34 2025 +0100
Fix guc_malloc calls for consistency and OOM checks
Author: Daniel Gustafsson <daniel@yesql.se>
Reported-by: Nikita <pm91.arapov@gmail.com>
Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
Bug: #18845
Discussion: /messages/by-id/18845-582c6e10247377ec@postgresql.org
Backpatch-through: 16

maybe we can credit it to
Nikita <pm91.arapov@gmail.com>

Wenhui Qiu
wenhui qiu
I use ``git log --grep='Wenhui Qiu' `` can not find any result.
I think ``wenhui qiu`` is the correct one.

Zhihong Yu
Ted Yu
refers to the same person too.

Álvaro Herrera
Alvaro Herrera
refers to the same person.

Hou Zhijie
Zhijie Hou
refers to the same person.

Zharkov Roman
Roman Zharkov
refers to the same person, by comparing email address

Yuki Seino
Seino Yuki
refers to the same person, by comparing email address

hi.

Kuroda Hayato
Hayato Kuroda
refers to the same person.

Takatsuka Haruka
Haruka Takatsuka
refers to the same person.

I think that "Rainier Vilela" is a mistake and should be removed.
The correct is "Ranier Vilela"

best regards,
Ranier Vilela

I trust your expertise in this matter.

Apologies, several email responses went to just individuals instead of the
group.

On Wed, Sep 10, 2025 at 10:50 PM jian he <jian.universality@gmail.com>
wrote:

hi.

Nikita
Nikita Kalinin
Nikita Malakhov
The first "Nikita" refers to the commit below
058b5152f02ef86c98a795c14dbd6a8e195f4fd1.

maybe we can credit it to
Nikita <pm91.arapov@gmail.com>

The email address associated doesn't show up elsewhere, so I left it just
"Nikita".

Zhihong Yu
Ted Yu
refers to the same person too.

I'm inclined to believe you, but can you cite a link between the two?
Especially one that shows a name preference.

Hou Zhijie
Zhijie Hou
refers to the same person.

Went with Hou Zhijie based on email signature.

Yuki Seino
Seino Yuki
refers to the same person, by comparing email address

Went with Yuki Seino based on email signature.

On Thu, Sep 11, 2025 at 12:35 AM jian he <jian.universality@gmail.com>
wrote:

hi.

Kuroda Hayato
Hayato Kuroda
refers to the same person.

Takatsuka Haruka
Haruka Takatsuka
refers to the same person.

Fixed.

Fixed.

More than a few acknowledgements of edits went reply instead of reply-all,
but I think they've been addressed.

Down to 505 contributors from 516 in v18.

Updated credits list and full-outer-join diff lists attached.

Corey Huinker <corey.huinker@gmail.com> writes:

On Wed, Sep 10, 2025 at 10:50 PM jian he <jian.universality@gmail.com>
wrote:

Zhihong Yu
Ted Yu
refers to the same person too.

I'm inclined to believe you, but can you cite a link between the two?
Especially one that shows a name preference.

The forms that appear in my local archives are

Zhihong Yu <zyu@yugabyte.com>
Ted Yu <yuzhihong@gmail.com>

While that's not evidence that would satisfy a court of law, it's
close enough for the purpose at hand.

The yugabyte.com address doesn't seem to have been active since 2022
though; recent references to it are only in messages doing
reply-to-all. I'd go with the gmail address as being current,
and therefore with "Ted" as being the person's current preference,
barring input to the contrary.

Yuki Seino
Seino Yuki
refers to the same person, by comparing email address

Went with Yuki Seino based on email signature.

Westerners tend to have a hard time distinguishing given name
from family name in Eastern names, and the lack of consistency
about that in email signatures doesn't help :-(. Our intention
in the release notes is to write given names first, but I'm sure
we've made many mistakes of that sort. Perhaps some of our
Eastern colleagues can offer some help about which way to spell
these. (Checking past iterations of the release notes could
be helpful, too.)

regards, tom lane

On Thu, 11 Sept 2025 at 14:28, Corey Huinker <corey.huinker@gmail.com>
wrote:

Fixed.

More than a few acknowledgements of edits went reply instead of

reply-all, but I think they've been addressed.

Thanks for working on this:

These (reported earlier) still exist:
Kuroda Hayato vs Hayato Kuroda
Roman Zharkov vs Zharkov Roman

Unsure if this is the same person:
"Dmitry Koval" "Dmitry Kovalenko"

This line is probably unnecessary:
newtglobal postgresql_contributors

-
robins

These (reported earlier) still exist:
Kuroda Hayato vs Hayato Kuroda
Roman Zharkov vs Zharkov Roman

Fixed.

Unsure if this is the same person:
"Dmitry Koval" "Dmitry Kovalenko"

Might be. I defer to the 1-2 subject matter expert(s).

This line is probably unnecessary:
newtglobal postgresql_contributors

Yeah, that's a strange one. It's definitely an attribution, so it stays,
but I have no opinion about whether it makes it into the SGML.

Corey Huinker <corey.huinker@gmail.com> writes:

This line is probably unnecessary:
newtglobal postgresql_contributors

Yeah, that's a strange one. It's definitely an attribution, so it stays,
but I have no opinion about whether it makes it into the SGML.

This seems to have been an alias used by an indeterminate group of
people, eg here:

/messages/by-id/174176421219.294105.3395783202038263246.pgcf@coridan.postgresql.org

I see only a few of these in the archives, so my preference is to just
drop it not try to trace down exactly who was behind the alias. In
general our intention is to credit actual individuals in the release
notes, so this doesn't qualify.

regards, tom lane

Hello everyone!
Apologies for jumping in with an unrelated question — I just happened
to see this email. For the acknowledgment list, is the cutoff point the date of the
PostgreSQL 18 official release (September 25, 2025), or does it refer to an earlier date?
—
Regards
Haiyang Li

"=?UTF-8?B?5p2O5rW35rSLKOmZjOeXlSk=?=" <mohen.lhy@alibaba-inc.com> writes:

Apologies for jumping in with an unrelated question — I just happened
to see this email. For the acknowledgment list, is the cutoff point the date of the
PostgreSQL 18 official release (September 25, 2025), or does it refer to an earlier date?

I'm not sure that we have an official policy on that point.
My own take on it would be "are you mentioned in the commit
log leading up to 18.0?" (or some slightly-earlier point where
the release notes are finalized). It's not really about dates
but about contributions to that branch; otherwise we might be
falsely crediting people who worked on 19.x but not 18.x.

Also ... in the big scheme of things, we are way more interested
in crediting ongoing contributors than single events. So if
you're there in the 19, 20, etc release notes but not 18.0,
I think you should be okay with that. Everybody started sometime.

regards, tom lane

On 11 Sep 2025, at 08:50, Tom Lane <tgl@sss.pgh.pa.us> wrote:

It's not really about dates but about contributions to that branch;

+1

--
Daniel Gustafsson

On 9/10/25 19:30, Daniel Gustafsson wrote:

There are a few first-names-only that need to be verified, IME they resolve to
a name already on the list.

Andrew
Dmitry
Felix

Regarding Dmitry.

If we are talking about this commit
c70b6db34ffeab48beef1fb4ce61bcad3772b8dd,
then this is Dmitry Yurichev.

I'm only the author of the issue here,
and the patch and commit itself were done by Yugo Nagata and Dean Rasheed.

commit c70b6db34ffeab48beef1fb4ce61bcad3772b8dd
Author: Dean Rasheed <dean.a.rasheed@gmail.com>
Date:   Fri Sep 5 08:21:35 2025 +0100

    Fix concurrent update issue with MERGE.

    Reported-by: Dmitry <dsy.075@yandex.ru>
    Author: Yugo Nagata <nagata@sraoss.co.jp>
    Reviewed-by: Dean Rasheed <dean.a.rasheed@gmail.com>
    Reviewed-by: Chao Li <li.evan.chao@gmail.com>
    Discussion:
/messages/by-id/1570d30e-2b95-4239-b9c3-f7bf2f2f8556@yandex.ru
    Backpatch-through: 15

--
Best regards,
Dmitry Yurichev.

On Thu, Sep 11, 2025 at 2:23 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:

Corey Huinker <corey.huinker@gmail.com> writes:

On Wed, Sep 10, 2025 at 10:50 PM jian he <jian.universality@gmail.com>
wrote:

Yuki Seino
Seino Yuki
refers to the same person, by comparing email address

Went with Yuki Seino based on email signature.

Right, "Yuki" is his given name.

Westerners tend to have a hard time distinguishing given name
from family name in Eastern names, and the lack of consistency
about that in email signatures doesn't help :-(. Our intention
in the release notes is to write given names first, but I'm sure
we've made many mistakes of that sort. Perhaps some of our
Eastern colleagues can offer some help about which way to spell
these. (Checking past iterations of the release notes could
be helpful, too.)

These are in the wrong order (surname followed by given name):

Katsuragi Yuta
Kuroda Hayato
Sutou Kouhei
Takatsuka Haruka

Thanks for working on this!

Best regards,
Etsuro Fujita

Regarding Dmitry.

If we are talking about this commit
c70b6db34ffeab48beef1fb4ce61bcad3772b8dd,
then this is Dmitry Yurichev.

Updated. That does appear to have been the last last-name-less Dmitry
mention or attribution remaining.

These are in the wrong order (surname followed by given name):

Katsuragi Yuta
Kuroda Hayato
Sutou Kouhei
Takatsuka Haruka

These have been updated. I'm holding off on releasing the update files
pending Daniel sending me a list of known preferred names. I'll release
another file after I've integrated that list into my process.

Hello!
I just happened to notice this message, and I’m certain they are
different people as both of them are my colleagues.

Unsure if this is the same person:
"Dmitry Koval" "Dmitry Kovalenko"

Might be. I defer to the 1-2 subject matter expert(s).

--
Ekaterina Kiryanova
Technical Writer
Postgres Professional
the Russian PostgreSQL Company

These have been updated. I'm holding off on releasing the update files
pending Daniel sending me a list of known preferred names. I'll release
another file after I've integrated that list into my process.

So here's the remaining one-name attributions:

commit_hash name email

---------------------------------------- --------
-----------------------------
67a2fbb8f9e9f75df08208e75da412c43a814688 RyotaK ryotak.mail@gmail.com

31c09ef4563612467b31149713896948e5532684
alexander.kjall@hafslund.no
7b1053a577494871acb5e91c63abb2bade5b8dea Andrew psy2000usa@yahoo.com

d47f922246b54f0290811951e0b73a3d6110437c Kaimeh kkaimeh@gmail.com

058b5152f02ef86c98a795c14dbd6a8e195f4fd1 Nikita pm91.arapov@gmail.com

901a1cf8b4a291a3a22021bf7acb516c1d278e53 Felix afripowered@gmail.com

4f15759bdcddd23e874526a6b2c0ff86e0beb042 anani191181515@gmail.com

6313a76b355e3640aba4cc80456a65c2bbc55a80 Asphator asphator@gmail.com

1eb5564230a3b82f7f8e8b91b93114dbde66c811 k.man.113@gmail.com

17b4aa77c3a161a9d0e7b08bd9931fe9fd051540 shixiong327926@gmail.com

I'm inclined to just delete these as far as credits are concerned as they
probably aren't a single person:

38c579b08988e6f1a5bd74241d0a1001421d8015 rootcause000@gmail.com

adf97c1562380e02acd60dc859c289ed3a8352ee Tels
nospam-pg-abuse@bloodgate.com

Likewise, not a likely single person:

newtglobal postgresql_contributors
postgresql_contributors@newtglobalcorp.com

So here's the updated.

This was done against the git log REL_17_STABLE..REL_18_STABLE,
as of 2d756ebbe857e3d395d18350bf232300ebd23981 on master and
a7024398b80a836a83c00af42c6ab7cc25c12087 on REL_18_STABLE.

On 18 Sep 2025, at 07:02, Corey Huinker <corey.huinker@gmail.com> wrote:

These have been updated. I'm holding off on releasing the update files pending Daniel sending me a list of known preferred names. I'll release another file after I've integrated that list into my process.

Thanks for working on this!

So here's the remaining one-name attributions:

commit_hash name email
---------------------------------------- -------- -----------------------------
67a2fbb8f9e9f75df08208e75da412c43a814688 RyotaK ryotak.mail@gmail.com
31c09ef4563612467b31149713896948e5532684 alexander.kjall@hafslund.no
7b1053a577494871acb5e91c63abb2bade5b8dea Andrew psy2000usa@yahoo.com
d47f922246b54f0290811951e0b73a3d6110437c Kaimeh kkaimeh@gmail.com
058b5152f02ef86c98a795c14dbd6a8e195f4fd1 Nikita pm91.arapov@gmail.com
901a1cf8b4a291a3a22021bf7acb516c1d278e53 Felix afripowered@gmail.com
4f15759bdcddd23e874526a6b2c0ff86e0beb042 anani191181515@gmail.com
6313a76b355e3640aba4cc80456a65c2bbc55a80 Asphator asphator@gmail.com
1eb5564230a3b82f7f8e8b91b93114dbde66c811 k.man.113@gmail.com
17b4aa77c3a161a9d0e7b08bd9931fe9fd051540 shixiong327926@gmail.com

Cross-referencing my list I found a few more which should be looked at:

1ab67c9dfaadda86059f405e5746efb6ddb9fe21
Author: vaibhave postgres <postgresvaibhave@gmail.com>

68dfecbef210dc000271553cfcb2342989d4ca0f
Reporter: usamoi@outlook.com

1afe31f03cd268a0bbb7a340d56b8eef6419bcb0
Reporter: wizardbrony@gmail.com

cf4401fe6cf56811343edcad29c96086c2c66481
Author: wuchengwen <drec.wu@foxmail.com>
(wuchengwen from the patch, 清浅 in the email)

Previous years notes do not include names where we only know the email address,
not sure what our policy on that is. Personally I think they should be
included, they are credited in the commitlog so they clearly belong in the
acknowledgments.

--
Daniel Gustafsson

On 2025-Sep-18, Corey Huinker wrote:

Álvaro Mongil

Hmm, where does this name come from? I can't find it anywhere.

[... trolls logs ...] ah, did you get it on private email from
alvaro@datadoghq.com ?

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
Si no sabes adonde vas, es muy probable que acabes en otra parte.

On 18 Sep 2025, at 11:23, Álvaro Herrera <alvherre@kurilemu.de> wrote:

On 2025-Sep-18, Corey Huinker wrote:

Álvaro Mongil

Hmm, where does this name come from? I can't find it anywhere.

[... trolls logs ...] ah, did you get it on private email from
alvaro@datadoghq.com ?

Thats correct (this name comes from my list of names that Corey referred to).

--
Daniel Gustafsson

On 18.09.25 10:14, Daniel Gustafsson wrote:

On 18 Sep 2025, at 07:02, Corey Huinker <corey.huinker@gmail.com> wrote:

These have been updated. I'm holding off on releasing the update files pending Daniel sending me a list of known preferred names. I'll release another file after I've integrated that list into my process.

Thanks for working on this!

Now is anyone planning to commit this? I can do it if no one else is
lined up.

Previous years notes do not include names where we only know the email address,
not sure what our policy on that is. Personally I think they should be
included, they are credited in the commitlog so they clearly belong in the
acknowledgments.

The policy was that we only included persons whose name we know. The
reason being, if they don't want to be known, then they also don't need
to be listed in the credits.

On 18 Sep 2025, at 14:25, Peter Eisentraut <peter@eisentraut.org> wrote:

On 18.09.25 10:14, Daniel Gustafsson wrote:

On 18 Sep 2025, at 07:02, Corey Huinker <corey.huinker@gmail.com> wrote:
These have been updated. I'm holding off on releasing the update files pending Daniel sending me a list of known preferred names. I'll release another file after I've integrated that list into my process.

Thanks for working on this!

Now is anyone planning to commit this? I can do it if no one else is lined up.

I was thinking we should wait for more timezones to have a chance to dig into
the list before committing. If you want to pick it up since you have a long
history of doing the list, feel free, else I can take care of it.

Previous years notes do not include names where we only know the email address,
not sure what our policy on that is. Personally I think they should be
included, they are credited in the commitlog so they clearly belong in the
acknowledgments.

The policy was that we only included persons whose name we know. The reason being, if they don't want to be known, then they also don't need to be listed in the credits.

My take would be that if they don't want to be known, they wouldn't have
contacted us in the first place. However, if we have a policy in place then
sticking to it makes us consistent and consistency is good.

--
Daniel Gustafsson

On Thu, Sep 18, 2025 at 1:02 PM Corey Huinker <corey.huinker@gmail.com> wrote:

So here's the updated.

This was done against the git log REL_17_STABLE..REL_18_STABLE,
as of 2d756ebbe857e3d395d18350bf232300ebd23981 on master and a7024398b80a836a83c00af42c6ab7cc25c12087 on REL_18_STABLE.

Hacking Discord
should be removed.

On Sun, Aug 17, 2025 at 11:57:50AM +0800, jian he wrote:

hi.
maybe we should start working on this?

https://www.postgresql.org/developer/roadmap
says 18 will be released in September 2025.

Folks, our list of PG 18 "new features and enhancements" and
"Acknowledgments" is being added very late in the process. jian asked
about this in mid-August, and I did the same in late August:

/messages/by-id/aLMo7lJKg8bWUs3y@momjian.us

I can't think of any good reason we are having to rush to complete this
when we knew and were warned months ago it was needed. Yes, it is
_slightly_ easier to do it only once rather than do it early and keep it
updated, but there isn't that a great a benefit that we should be
waiting until the last few days to complete this.

--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.

On Thu, Sep 18, 2025 at 11:13 AM Bruce Momjian <bruce@momjian.us> wrote:

I can't think of any good reason we are having to rush to complete this
when we knew and were warned months ago it was needed. Yes, it is
_slightly_ easier to do it only once rather than do it early and keep it
updated, but there isn't that a great a benefit that we should be
waiting until the last few days to complete this.

I complained about this same problem yesterday on another thread.

--
Robert Haas
EDB: http://www.enterprisedb.com

On Thu, Sep 18, 2025 at 11:18:04AM -0400, Robert Haas wrote:

On Thu, Sep 18, 2025 at 11:13 AM Bruce Momjian <bruce@momjian.us> wrote:

I can't think of any good reason we are having to rush to complete this
when we knew and were warned months ago it was needed. Yes, it is
_slightly_ easier to do it only once rather than do it early and keep it
updated, but there isn't that a great a benefit that we should be
waiting until the last few days to complete this.

I complained about this same problem yesterday on another thread.

Yeah, I saw. I was trying to find older references to show that waiting
this long just makes the job harder since there is less time for
adjustment, and people are getting nervous.

--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.

On Thu, Sep 18, 2025 at 1:02 PM Corey Huinker <corey.huinker@gmail.com> wrote:

So here's the updated.

This was done against the git log REL_17_STABLE..REL_18_STABLE,
as of 2d756ebbe857e3d395d18350bf232300ebd23981 on master and a7024398b80a836a83c00af42c6ab7cc25c12087 on REL_18_STABLE.

hi.
I double checked all the new names (in PG18, not in PG17) again.

all looks good, except that I can can not found these 3 names:
Emanuel Ionescu (do you mean commit 4200fea80e79851994b8eb5a64a3d4420456c977)
Jorge Solórzano
Gunnar Wagner

On Thu, Sep 18, 2025 at 9:33 AM jian he <jian.universality@gmail.com> wrote:

On Thu, Sep 18, 2025 at 1:02 PM Corey Huinker <corey.huinker@gmail.com>
wrote:

So here's the updated.

This was done against the git log REL_17_STABLE..REL_18_STABLE,
as of 2d756ebbe857e3d395d18350bf232300ebd23981 on master and

a7024398b80a836a83c00af42c6ab7cc25c12087 on REL_18_STABLE.

Hacking Discord
should be removed.

Grrrr. I thought I added that to my "things that regex like a name but
aren't" list. Thanks.

all looks good, except that I can can not found these 3 names:
Emanuel Ionescu (do you mean commit
4200fea80e79851994b8eb5a64a3d4420456c977)
Jorge Solórzano
Gunnar Wagner

I think those all came from Daniel's list of corrections, which didn't have
commit granularity.

I was thinking we should wait for more timezones to have a chance to dig
into
the list before committing. If you want to pick it up since you have a
long
history of doing the list, feel free, else I can take care of it.

Fire Emerald replied to Álvaro and myself off-list, saying they preferred
that nickname over any real name.

With that, I think the only change since the last drop is the removal of
Hacking Discord, which my scanner read as a name alias/qualifier like Jane
Doe (BIg Megacorp), so I think we're done.

On 19.09.25 14:52, Corey Huinker wrote:

I was thinking we should wait for more timezones to have a chance to
dig into
the list before committing.  If you want to pick it up since you
have a long
history of doing the list, feel free, else I can take care of it.

Fire Emerald replied to Álvaro and myself off-list, saying they
preferred that nickname over any real name.

With that, I think the only change since the last drop is the removal of
Hacking Discord, which my scanner read as a name alias/qualifier
like Jane Doe (BIg Megacorp), so I think we're done.

I have committed your v18 list, with the removal of "Hacking Discord".
I also removed "newtglobal postgresql_contributors", which is not an
individual.

Beyond that, the postprocessing steps were:

- sort list by collate "en-x-icu"
- add XML markup (sed -r 's,.*, <member>&</member>,')
- remove non-Latin1 characters until fop is happy

Hi,

With that, I think the only change since the last drop is the removal of Hacking Discord, which my scanner read as a name alias/qualifier like Jane Doe (BIg Megacorp), so I think we're done.

FWIW the following entries look the same to me:

+    <member>Andrew</member>
+    <member>Felix</member>
+    <member>Nikita</member>

It's like "John". These entries don't seem to reference any particular person.

--
Best regards,
Aleksander Alekseev

On Fri, Sep 19, 2025 at 8:58 AM Aleksander Alekseev <
aleksander@tigerdata.com> wrote:

Hi,

With that, I think the only change since the last drop is the removal of

Hacking Discord, which my scanner read as a name alias/qualifier like Jane
Doe (BIg Megacorp), so I think we're done.

FWIW the following entries look the same to me:

+    <member>Andrew</member>
+    <member>Felix</member>
+    <member>Nikita</member>

It's like "John". These entries don't seem to reference any particular
person.

They are. I checked thread history, and we chased all three names down the
rabbit hole, and found no last name. Email addresses matter in other
situations, but not release credits. I trust the committers to handle them
as they see fit.

I think that the policies for how to handle names in this list are evolving
as the community grows, and I have a few ideas for how to make this process
smoother next time around, with some procedures for asking the contributors
themselves how they want to be attributed well in advance of the release
date.