Problem/Motivation
As of September 2015 we have all tests passing the PostgreSQL CI bot (yay!). However, there are still some open issues around that should be fixed in terms of performance, security and for contrib land. As a first start here is the list of open issues copied over from #2157455: [Meta] Make Drupal 8 work with PostgreSQL or remove support from core before release.

Bugs:

Performance issues:

Security issues:

  • none!

Feature request:

Other issues:

Done:

Comments

bzrudi71 created an issue. See original summary.

bzrudi71’s picture

Issue summary: View changes
bzrudi71’s picture

Issue summary: View changes
bzrudi71’s picture

Issue summary: View changes
bzrudi71’s picture

Issue summary: View changes

Housecleaning and some new issues.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

joelpittet’s picture

Category: Task » Plan
bzrudi71’s picture

Issue summary: View changes

Housecleaning

bzrudi71’s picture

Issue summary: View changes

Removing #1349080: node_access filters out accessible nodes when node is left joined from list as it's not really PostgreSQL specific...

daffie’s picture

Issue summary: View changes

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

daffie’s picture

Added issue #2850684: Default Database Schema::fieldExists() is slow for PostgreSQL. The testbot finishes with this patch a lot faster:

  1. PostgreSQL + PHP 5.5 is 10 minutes faster
  2. PostgreSQL + PHP 5.6 is 4 minutes faster
  3. PostgreSQL + PHP 7 is 8 minutes faster

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

rosk0’s picture

daffie’s picture

rosk0’s picture

Issue summary: View changes

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

bzrudi71’s picture

bzrudi71’s picture

Issue summary: View changes

#2921665: PostgreSQL: Optimize getting maxIdentifierLength is is committed - moved out of todo :)

bzrudi71’s picture

qpro’s picture

rosk0’s picture

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

cilefen’s picture

rosk0’s picture

andypost’s picture

I bet nobody has ?? operator cos this will be issue with php 7.4 https://wiki.php.net/rfc/pdo_escape_placeholders

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

andypost’s picture

badrange’s picture

Should we rename this issue to "Remaining Drupal 9 issues"? It will make the issue seem more up to date than referencing Drupal 8.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

andypost’s picture

m.stenta’s picture

Title: [meta] Remaining Drupal 8 PostgreSQL issues » [meta] Remaining Drupal 8/9 PostgreSQL issues

+1 to @badrange's suggestion. Renaming to "[meta] Remaining Drupal 8/9 PostgreSQL issues".

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

penyaskito’s picture

Aside of case insensitivity, handled in #2464481: PostgreSQL: deal with case insensitivity, is there any issue created for handling with "unaccent" for parity with MySQL?

guignonv’s picture

Issue summary: View changes
rosk0’s picture

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

orkutmuratyilmaz’s picture

Issue summary: View changes
orkutmuratyilmaz’s picture

Issue summary: View changes
orkutmuratyilmaz’s picture

Sorry for the notifications you have received since last Friday. I've thought that I've found a bug, but after checking later, I understood that I haven't.

Thanks a lot for the contributions you've been doing.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

andypost’s picture

Title: [meta] Remaining Drupal 8/9 PostgreSQL issues » [meta] Remaining Drupal 9/10 PostgreSQL issues
m.stenta’s picture

I just opened this issue - curious if it should be added to the list, or closed as "works as designed"... still understanding it... if anyone here has experience or knowledge it would be welcome!

#3318915: PostgreSQL errors: duplicate key value violates unique constraint (key_value____pkey and semaphore____pkey)

xurizaemon’s picture

Issue summary: View changes

For Postgres-backed sites, I see an SQL error triggered when accessing a path with entity IDs in the range 2147483648 to 9223372036854776832 (eg /node/{id}, /user/{id}, /taxonomy/term/{id} ...). A 404 should be returned when the entity ID does not exist, and is correctly returned when the ID is not in that range OR the site is not postgres-backed.

#3327520: Postgres error 500 on paths when supplied entity ID gte 2147483647 and lte 9223372036854776832 has details and a test which I believe shows the incorrect behaviour; test has failed (as expected) on pgsql and passed on mysql (tested postgres, mysql and sqlite locally).

daffie’s picture

daffie’s picture

daffie’s picture

Issue summary: View changes

Removed #3018025: Views aggregation functions SUM, AVERAGE and STDDEV_POP causes "Undefined function error" when are used in some fields in postgresql from the list as it is not related to PostgreSQL. They are trying to SUM on a string field. It is a views bug.

chi’s picture

Issue summary: View changes

Added a couple relevant issues

user654’s picture

.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

daffie’s picture

@pinkonomy: Any help with getting the PostgreSQL issues fixed will be greatly appreciated. So, please help. I will help by reviewing the patches/MR.

andypost’s picture

orkutmuratyilmaz’s picture

@pinkonomy, I've seen this in #ai channel.

By the way, there is no #postgresql channel on https://drupal.org/slack and I think that we need one:)

orkutmuratyilmaz’s picture

Can we add this issue to the list?

liam morland’s picture

liam morland’s picture

Title: [meta] Remaining Drupal 9/10 PostgreSQL issues » [meta] Remaining Drupal 10/11 PostgreSQL issues
quietone’s picture

Issue summary: View changes

Move completed items to "done' section.

andypost’s picture

I gonna upgrade CI docker images to latest 15.6/16.2 follow #3421217: Upgrade Postgresql 15.6/16/2

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.