Re: Why does pgindent's README say to download typedefs.list from the buildfarm?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Nathan Bossart <nathandbossart@gmail.com>, pgsql-hackers@postgresql.org
Date: 2024-05-15T20:23:23Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes: > On Wed, May 15, 2024 at 3:30 PM Nathan Bossart <nathandbossart@gmail.com> wrote: >> This is much cleaner, thanks. The only thing that stands out to me is that >> the "once per release cycle" section should probably say to do an indent >> run after downloading the typedef file. > How's this? This works for me. One point that could stand discussion while we're here is whether the once-a-cycle run should use the verbatim buildfarm results or it's okay to editorialize on that typedefs list. I did a little of the latter in da256a4a7, and I feel like we should either bless that practice in this document or decide that it was a bad idea. For reference, what I added to the buildfarm's list was +InjectionPointCacheEntry +InjectionPointCondition +InjectionPointConditionType +InjectionPointEntry +InjectionPointSharedState +NotificationHash +ReadBuffersFlags +ResourceOwnerData +WaitEventExtension +WalSyncMethod I believe all of these must have been added manually during v17. If I took any one of them out there was some visible disimprovement in pgindent's results, so I kept them. Was that the right decision? If so we should explain it here. regards, tom lane
Commits
-
Sync typedefs.list with buildfarm, for real this time.
- 70353e463cd3 17.0 landed
-
Remove unused typedefs
- be5942aee7a0 17.0 landed
-
Remove enum WaitEventExtension
- 110eb4aefbad 17.0 landed
-
Add pgindent typedefs file to CVS.
- 16040575a044 9.0.0 cited