SilverStripe now has tentative support for PostgreSQL ('Postgres')
Installs: 246 627
Open Issues: 12
- ext-pgsql: *
- silverstripe/framework: ^5
- silverstripe/vendor-plugin: ^2
- phpunit/phpunit: ^9.5
- squizlabs/php_codesniffer: ^3
- 1.x-dev / 1.3.x-dev
This package is auto-updated.
Last update: 2023-05-24 00:11:50 UTC
- Silverstripe 4.0
- PostgreSQL >=9.2
- Note: PostgreSQL 10 has not been tested
composer require silverstripe/postgresql
Add the following settings to your
SS_DATABASE_CLASS=PostgreSQLDatabase SS_DATABASE_USERNAME= SS_DATABASE_PASSWORD=
See environment variables for more details. Note that a database will automatically be created via
Through the installer
Open the installer by browsing to install.php, e.g. http://localhost/install.php Select PostgreSQL in the database list and enter your database details
See docs/en for more information about configuring the module.
All column and table names must be double-quoted. PostgreSQL automatically lower-cases columns, and your queries will fail if you don't.
Collations have known issues when installed on Alpine, MacOS X and BSD derivatives (see PostgreSQL FAQ). We do not support such installations, although they still may work correctly for you. As a workaround for PostgreSQL 10+ you could manually switch to ICU collations (e.g. und-x-icu). There are no known workarounds for PostgreSQL <10.
Ts_vector columns are not automatically detected by the built-in search filters. That means if you're doing a search through the CMS on a ModelAdmin object, it will use LIKE queries which are very slow. If you're writing your own front-end search system, you can specify the columns to use for search purposes, and you get the full benefits of T-Search.
If you are using unsupported modules, there may be instances of MySQL-specific SQL queries which will need to be made database-agnostic where possible.