CARVIEW

MOTORHOMES

Select Language

HTTP/2 200 server: GitHub.com content-type: text/html; charset=utf-8 last-modified: Thu, 17 Jul 2025 20:49:58 GMT access-control-allow-origin: * etag: W/"687961f6-107c" expires: Mon, 28 Jul 2025 16:28:47 GMT cache-control: max-age=600 content-encoding: gzip x-proxy-cache: MISS x-github-request-id: 5B77:230167:118ED5:14507C:6887A2E6 accept-ranges: bytes age: 0 date: Mon, 28 Jul 2025 16:18:47 GMT via: 1.1 varnish x-served-by: cache-bom-vanm7210062-BOM x-cache: MISS x-cache-hits: 0 x-timer: S1753719528.710693,VS0,VE218 vary: Accept-Encoding x-fastly-request-id: c60bbfda6bf17fd43788d9da74cf132c42140b8a content-length: 1544 Why you should place Postgres.app inside your Applications folder

Postgres.app

The easiest way to get started with PostgreSQL on the Mac

Why you should place Postgres.app inside your Applications folder

Postgres.app is designed to run from /Applications. Beginning with Postgres.app version 2.6, you can start it from other locations, but some features might not work correctly.

Linking software with libraries provided by Postgres.app will not work. This means installing the ruby gem pg or the Python library psycopg2 will not work.
Building custom extensions that are not included with Postgres.app will not work
on macOS 12 and earlier, automatic start of PostgreSQL servers won’t work

Launching Postgres.app directly from the disk image

It is possible to lauch Postgres.app directly from the disk image, with the limitations above, and two extra limitations:

automatic updates do not work if the app is launched from the disk image
automatc starting of PostgreSQL servers in the background does not work if the app is launched from the disk image
all the limitations above apply as well

For more details, see issue #693

Original Source | Taken Source