Tobias Bussmann

From the message it seems you compiled the extension for arm64 while postgres is currently still x86_64, thus you can't link them. Likely, you need to supply some flags to...

In general PostgresApp does allow building own extensions against it, given the necessary compilers and dependencies are available, our distribution provides a working `pg_config`. Please make sure [you configured your...

Some additional details on when this may be (not) need: You are not affected if: * the database cluster ('Server' in PostgresApp) was initialised on macOS 11 or later *...

The mitigations outlined above have been released with Postgres.app v2.5.7 and a [dedicated page](https://postgresapp.com/l/reindex_warning) has been added to the documentation.

> For some reason the DYLD_LIBRARY_PATH variable has no effect. postgres has the correct entitlements, but maybe the env var gets lost when forking or something. We need to investigate...

Can't we use approach 3 with a location within our application bundle like `/Applications/Postgres.app/Contents/Versions/13/lib/myPython3` that later can be symlinked to the actual lib with the user's permissions?

I wasn't aware of the specific amplification of this issue caused by the fact that PostgresApp does not run as a dedicated user. Thanks for pointing this out! Beside being...

As with most extensions it is not to hard to build them against the PostgresApp distribution. If you are comfortable with homebrew to provide the dependencies, you can roughly follow...

...and a way to force it's installation (in case it is not triggered automatically) is mentioned [here](https://derflounder.wordpress.com/2020/11/17/installing-rosetta-2-on-apple-silicon-macs/): `/usr/sbin/softwareupdate --install-rosetta` We should find out why it is not triggered, thus.

Thanks for your feedback and interest on using `postgis_sfcgal` with PostgresApp. Adding this extension to the distribution is definitely on the ToDo list. Complementary compiling this on the users end...