[1] Engine Configuration — SQLAlchemy 0.7 Documentation ( ( 版)) <>

[2] PostgreSQL: Documentation: 9.2: Database Connection Control Functions ( ( 版)) <>

[3] PostgreSQL: Documentation: 9.5: Database Connection Control Functions () <>

[4] '/' is not allowed in domains · Issue #26 · servo/rust-url () <>

[5] Heroku Postgres | Heroku Dev Center () <>

Once Heroku Postgres has been added a DATABASE_URL or HEROKU_POSTGRESQL_COLOR_URL setting will be available in the app configuration and will contain the URL used to access the newly provisioned Heroku Postgres service. DATABASE_URL will be given to the database if it is the first one for the application, otherwise the HEROKU_POSTGRESQL_COLOR_URL will be created. This can be confirmed using the heroku config command.

$ heroku config -s | grep HEROKU_POSTGRESQL


[6] Configuring Rails Applications — Ruby on Rails Guides () <>

This same information can be stored in a URL and provided via an environment variable like this:



[7] The DB-URI — TurboGears 1.0 documentation () <>

If your Linux or OS X installation has a standard setup and there’s a live socket at /tmp/.s.PGSQL.5432, your SQLAlchemy PostgreSQL dburi can be this simple:


To specify the socket file for PostgreSQL, put the absolute path after the double slash:


However, there are bugs in the DSN parser for SQLObject, so that it fails to separate the socket path from the database name. A DSN like this works around that issue: