model-writtenrun 9038 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Andrew Dunstan proposed allowing sslkey and sslcert in postgres_fdw user mappings, with mapping settings overriding server settings, and added option-validation tests including sslpassword coverage #1.
- Progress depended on the separate passwordless-user-mapping patch, which Andrew explained was still awaiting broader support #3.
- After the prerequisite landed, Peter Eisentraut questioned the comment describing the option registration as a hack; Andrew rewrote the comment and announced that the feature was committed #4 #5.
- Christoph Berg identified that unprivileged users could supply arbitrary certificate-file paths and confirmed filesystem access with a trace; he proposed explicit superuser checks and separately suggested certificate strings as a possible alternative requiring libpq support #6 #7 #8.
- Robert Haas supported restricting arbitrary filesystem access, while Andrew initially questioned whether it exposed file contents; Daniel Gustafsson favored precautionary restrictions, and Tom Lane explained that probing file existence was itself unacceptable, convincing Andrew to add the checks #9 #10 #11 #12 #13.
- The discussion produced cebf9d6e6e, which restricts creating or modifying user mappings containing sslcert or sslkey to superusers, adds regression tests, and documents the restriction; no patch for this follow-up was attached.
- After the restriction landed, Craig Ringer endorsed it and described additional possible risks involving OpenSSL error output and FIFOs; the thread ended with the feature and security restriction committed, while certificate-string support remained only a suggestion #14 #7.