Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: How to statically compile PostgreSQL (for portablitiy) #4

Open
coolaj86 opened this issue Oct 12, 2024 · 0 comments
Open

doc: How to statically compile PostgreSQL (for portablitiy) #4

coolaj86 opened this issue Oct 12, 2024 · 0 comments

Comments

@coolaj86
Copy link

coolaj86 commented Oct 12, 2024

Scripts

Short Answer

The maintainers and other community members of Postgres have been clear that they believe static Postgres is far more harmful than not, and are not willing to support static builds.

Retooling the entire make system to support static builds would most likely not be accepted, and is not feasible for most people to do.

Long Answer: Bundle Instead

You can vendor the needed libraries into the ./lib/ folder and then update their rpaths in order to achieve nearly the same effect as static linking - or at least much greater compatibility across systems.

This is not considered static, but may be considered portable or relocatable.

The instructions vary slightly by architecture:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant