Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
PostgreSQL module for SilverStripe CMS. Allows SilverStripe to connect to, and use PostgreSQL as a database.
branch: master
Failed to load latest commit information.
_config NEW: Allow 'null' limit in database queries
code NEW: Allow 'null' limit in database queries
docs API Upgraded module to use new database ORM
tests API Upgraded module to use new database ORM
.editorconfig Adding .editorconfig
.travis.yml Don't test against unsupported core versions
CHANGELOG MINOR: changelog for the 0.9.2 release
LICENSE MINOR: Documentation update for the 0.9.1 release Alias dev-master as 1.2
_config.php API Upgraded module to use new database ORM
_register_database.php API Upgraded module to use new database ORM

PostgreSQL Module Module

Build Status

Maintainer Contact


  • SilverStripe 3.0
  • PostgreSQL 8.3.x or greater must be installed
  • PostgreSQL <8.3.0 may work if T-Search is manually installed
  • Known to work on OS X Leopard, Windows Server 2008 R2 and Linux


  1. Install via composer composer require silverstripe/postgresql 1.2.*-dev or extract the contents so they reside as a postgresql directory inside your SilverStripe project code
  2. Open the installer by browsing to install.php, e.g. http://localhost/silverstripe/install.php
  3. Select PostgreSQL in the database list and enter your database details

Usage Overview

See docs/en for more information about configuring the module.

Known issues

All column and table names must be double-quoted. PostgreSQL automatically lower-cases columns, and your queries will fail if you don't.

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.

Something went wrong with that request. Please try again.