Just cheked out today's HEAD, installed, and attempted to access main page. Results:
[client 10.10.59.23] PHP Notice: Undefined variable: _SESSION in /var/www/drupal_HEAD/includes/bootstrap.inc on line 771
[client 10.10.59.23] PHP Notice: Undefined variable: _SESSION in /var/www/drupal_HEAD/includes/bootstrap.inc on line 771
[client 10.10.59.23] PHP Notice: Undefined variable: _SESSION in /var/www/drupal_HEAD/includes/bootstrap.inc on line 771
[client 10.10.59.23] PHP Warning: pg_query(): Query failed: ERROR: syntax error at or near "cache" at character 13 in /var/www/drupal_HEAD/includes/database.pgsql.inc on line 69
[client 10.10.59.23] PHP Fatal error: ERROR: syntax error at or near "cache" at character 13\nquery: LOCK TABLES cache WRITE in /var/www/drupal_HEAD/includes/database.pgsql.inc on line 86
[client 10.10.59.23] PHP Notice: Undefined property: cache in /var/www/drupal_HEAD/includes/session.inc on line 45
[client 10.10.59.23] PHP Warning: pg_query(): Query failed: ERROR: syntax error at or near "cache" at character 13 in /var/www/drupal_HEAD/includes/database.pgsql.inc on line 69
[client 10.10.59.23] PHP Fatal error: ERROR: syntax error at or near "cache" at character 13\nquery: LOCK TABLES cache WRITE in /var/www/drupal_HEAD/includes/database.pgsql.inc on line 86
[client 10.10.59.23] PHP Warning: pg_query(): Query failed: ERROR: syntax error at or near "cache" at character 13 in /var/www/drupal_HEAD/includes/database.pgsql.inc on line 69
[client 10.10.59.23] PHP Fatal error: ERROR: syntax error at or near "cache" at character 13\nquery: LOCK TABLES cache WRITE in /var/www/drupal_HEAD/includes/database.pgsql.inc on line 86
This is because bootstap.inc uses LOCK/UNLOCK TABLES, but PostgreSQL does not support this syntax. I've attached a patch that fixes the problem on pgsql, but this probably still needs work as it most likely won't work on MySQL as such.
Comments
Comment #1
plj commentedActually, it seems there are two such problems (LOCK TABLES) in bootstrap.inc. Here is a better patch, that fixes them both. Same limitations apply as above, though.
Comment #2
plj commentedWhoops, managed to write 'EXCLUSIVE ACCESS' instead of 'ACCESS EXCLUSIVE'. And 'IN MODE' is not really necessary, as the strictest locking mode is default, if nothing is defined.
Here is a patch that actually works.
Unfortunately, it seems that there is no standard table locking syntax that both MySQL and PostgreSQL would accept. Perhaps we need some other way to implement cache_set() and variable_set()?
Comment #3
Cvbge commentedI've posted a fix for this in http://drupal.org/node/22911
I'm marking this one as duplicate.