Incremental Update: Committer Attribution Concern
The only new message is from Bruce Momjian, who attempted to commit the patch but hit a procedural/policy obstacle rather than a technical one.
The Issue
Bruce reports he was ready to apply the patch but could not fill in the Author field because the submitter's email name does not appear to be a person's name (it looks like a company/organization name). He states he is "uncomfortable committing something without a person's name" and cannot recall ever having done so. His rationale: without a personal name, there is no way to reference the original author in the future.
Options Bruce Proposes
- Apply the patch with no author attribution (if the community is comfortable with that precedent).
- Leave the comment typo unfixed entirely.
Significance
This is not a technical objection to the patch content — Bruce confirms he was ready to apply it. It is purely a commit metadata/attribution policy question. This is a rare but interesting procedural edge case for the PostgreSQL project:
- PostgreSQL's git history uses real names in Author fields (consistent with the project's long-standing contributor identification norms).
- The project does not have a formal CLA or DCO that would independently resolve identity questions, so committer judgment is the gatekeeper.
- The question of whether organizational/pseudonymous contributions can be accepted without a named individual is being surfaced here, albeit over a trivial patch.
No technical review of the patch content has occurred beyond Bruce's implicit approval by attempting to commit it.