This issue has been split from the parent/meta issue #2001350: [meta] Drupal cannot be installed on PostgreSQL.
Updated: Comment #2
Problem/Motivation
Cache tables are missing at the end of the installation. This produces a broken Drupal installation where menus, as one example, are not displayed.
Proposed resolution
Catch exceptions in deleteAll and deleteMultiple methods and create the cache table if it does not exist (cache_block and cache_menu). The approach was first discussed and accepted at Midwest Developer Summit 2013 (#66 in #2001350) rather than attempting to radically change block or menu or cache clearing during the installation.
Remaining tasks
None.
API changes
None.
Comment | File | Size | Author |
---|---|---|---|
#2 | drupal-2181289-postgres-cache-tables-1.patch | 1.16 KB | mradcliffe |
Comments
Comment #1
mradcliffeComment #2
mradcliffeCreated patch with solution split from parent issue, and updated the issue summary with a link to the comment discussing the approach.
Also this effects the cache system slightly so changing the component.
Comment #3
bzrudi71 CreditAttribution: bzrudi71 commentedJust applied patch and it works as expected. As this patch was accepted - as the way to go - we should get this in. Especially as PostgreSQL testbot is now up and running and the issue from PostgreSQL failed to connect seems gone.
Comment #4
mradcliffe2: drupal-2181289-postgres-cache-tables-1.patch queued for re-testing.
It's been a week. Making sure patch still applies.
Comment #5
mradcliffeClarified issue summary, set to RTBC as patch was reviewed and tested in this issue as well as in the meta issue for months.
Comment #6
webchickThis looks harmless to me, but juuuuuust in case, assigning to catch to eyeball, since he has more familiarity with the cache system.
Comment #7
catchYes this is fine. We already do the same thing for other cache operations, so it's just making the behaviour consistent.
Committed/pushed to 8.x, thanks!