Hi @michaelkuhn! I noticed that the following package(s) don't yet have maintainers:

• postgresql

Are you interested in adopting any of these package(s)? If so, simply add the following to the package class:

    maintainers("michaelkuhn")

If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with spack blame:

$ spack blame postgresql

Thank you for your help! Please don't add maintainers without their consent.

You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer.

If I read the docs correctly, it is only required for version 17 and optional for version <= 16. See https://www.postgresql.org/docs/17/install-requirements.html.

If I read the docs correctly, it is only required for version 17 and optional for version <= 16. See https://www.postgresql.org/docs/17/install-requirements.html.

Thanks for the hint, I hadn't noticed that. flex and bison also seem to be build dependencies, so I have updated all three.