Answers.Body: <p><strong>No.</strong></p>
  
  <p>CiviCRM uses MySQL functions extensively, so it can't be run with PostgreSQL.</p>
  
  <p>This has been raised before over on forum.civicrm.org (at least in <a href="https://forum.civicrm.org/index.php/topic,14103.0.html" rel="nofollow">2010</a> and <a href="https://forum.civicrm.org/index.php/topic,1079.0.html" rel="nofollow">2007</a>). Tim Otten's answer in <a href="https://forum.civicrm.org/index.php?topic=31846.0" rel="nofollow">this forum post</a> may also help understand some of the workings currently in the DB layer (and specific to MySQL).</p>
  
  <p>It could (in theory) be done, but it would take significant effort and leadership from the community who wanted to make it happen.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-11T18:21:44.973Z
Answers.Text: On reflection I feel confident those mysqlisms *could* be implemented in pg - but you'd have a high maintenance undertaking, and a small group of users to start with.
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-11T18:52:20.787Z
Answers.Text: It's a relatively new project, but it seems to me that over the long haul it would be of great benefit to the users to have PostgreSQL as an option for CiviCRM, simply because of how much data PostgreSQL can hold.
Answers.UserDisplayName: leeand00
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-11T20:11:50.133Z
Answers.Text: I agree - I'm not a big fan of CiviCRM's MySQLism, but it's the status quo. Similar to the [situation on WordPress](https://codex.wordpress.org/Using_Alternative_Databases), but with a much larger codebase and smaller pool of organisations to fund the work.
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-11T20:12:19.740Z
Answers.Text: If DB size limits are your concern, it's likely to be less work for you to contribute towards optimising CiviCRM on MySQL. MySQL can also handle significant data sets.
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-12T18:29:26.500Z
Answers.Text: I know a developer who's been working toward this as a side-project, although he hasn't published anything. If anyone is looking to collaborate on or fund such a project, email info-at-civicrm.org and I'll put you in touch.
Answers.UserDisplayName: Tim Otten
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-11T18:20:33.737Z
Answers.LastActivityDate: 2015-09-11T20:32:01.903Z
Answers.LastEditDate: 2015-09-11T20:32:01.903Z
Answers.UserDisplayName: Chris Burgess
Body: <p>Is there a version of CiviCRM that's compatible with Postgres and Wordpress?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-09-12T18:44:08.383Z
Comments.Text: Are you looking to run Civi-on-Postgres -- or to integrate Civi with (WordPress-on-Postgres). Although Civi puts its own tables in MySQL, it should be agnostic about the WordPress tables (modulo a few small patches/workarounds).
Comments.UserDisplayName: Tim Otten
Tags: <wordpress><database><evaluating-civicrm><compatiblity>
Title: Is CiviCRM compatible with Postgres and Wordpress?
ThreadText: # Is CiviCRM compatible with Postgres and Wordpress?
  
  (Asked by: username_0 on 2015-09-11)
  
  Is there a version of CiviCRM that's compatible with Postgres and Wordpress?
  
  **Tags:** wordpress, database, evaluating-civicrm, compatiblity
  
  > **Comments:**
  > **username_1**: Are you looking to run Civi-on-Postgres -- or to integrate Civi with (WordPress-on-Postgres). Although Civi puts its own tables in MySQL, it should be agnostic about the WordPress tables (modulo a few small patches/workarounds).  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2015-09-11. Score: 3 | Accepted answer
  
  **No.**
  
  CiviCRM uses MySQL functions extensively, so it can't be run with PostgreSQL.
  
  This has been raised before over on forum.civicrm.org (at least in [2010](https://forum.civicrm.org/index.php/topic,14103.0.html) and [2007](https://forum.civicrm.org/index.php/topic,1079.0.html)). username_1's answer in [this forum post](https://forum.civicrm.org/index.php?topic=31846.0) may also help understand some of the workings currently in the DB layer (and specific to MySQL).
  
  It could (in theory) be done, but it would take significant effort and leadership from the community who wanted to make it happen.
  
  > **Comments:**
  > **username_2**: On reflection I feel confident those mysqlisms *could* be implemented in pg - but you'd have a high maintenance undertaking, and a small group of users to start with.  
  > **username_0**: It's a relatively new project, but it seems to me that over the long haul it would be of great benefit to the users to have PostgreSQL as an option for CiviCRM, simply because of how much data PostgreSQL can hold.  
  > **username_2**: I agree - I'm not a big fan of CiviCRM's MySQLism, but it's the status quo. Similar to the [situation on WordPress](https://codex.wordpress.org/Using_Alternative_Databases), but with a much larger codebase and smaller pool of organisations to fund the work.  
  > **username_2**: If DB size limits are your concern, it's likely to be less work for you to contribute towards optimising CiviCRM on MySQL. MySQL can also handle significant data sets.  
  > **username_1**: I know a developer who's been working toward this as a side-project, although he hasn't published anything. If anyone is looking to collaborate on or fund such a project, email info-at-civicrm.org and I'll put you in touch.  
  
  ---
  
  