Not sure if this info might impact the outcome of this report or not, but this site ran on MySQL for a number of years before I recently migrated it to PostgreSQL. Since then, drush cron is failing, and sitename.com/cron.php does not produce any errors.

Out put of the error is:

WD php: pg_query(): Query failed: ERROR: LIMIT #,# syntax is not [error]
supported
HINT: Use separate LIMIT and OFFSET clauses. in
/home2/althusiu/public_html/includes/database.pgsql.inc on line 139.
WD php: [error]
query: SELECT u.uid, u.name, u.mail, fbr.email_hash FROM users u LEFT
JOIN fb_register fbr ON fbr.uid=u.uid WHERE (fbr.uid IS NULL OR u.uid
> 0) AND u.mail IS NOT NULL AND u.mail '' ORDER BY u.uid LIMIT 0,
100 in
/home2/althusiu/public_html/sites/all/modules/fb/contrib/fb_register.module
on line 174.
Cron run successfully. [success]
pg_query(): Query failed: ERROR: LIMIT #,# syntax is not supported [warning]
HINT: Use separate LIMIT and OFFSET clauses. in
/home2/althusiu/public_html/includes/database.pgsql.inc on line 139.
[error]
query: SELECT u.uid, u.name, u.mail, fbr.email_hash FROM users u LEFT
JOIN fb_register fbr ON fbr.uid=u.uid WHERE (fbr.uid IS NULL OR u.uid
> 0) AND u.mail IS NOT NULL AND u.mail <> '' ORDER
BY u.uid LIMIT 0, 100 in
/home2/althusiu/public_html/sites/all/modules/fb/contrib/fb_register.module
on line 174.
An error occurred at function : drush_core_cron

The errors are being report on stdout, rather than stderr, and it says cron ran successfully inspite of the errors.

Comments

timotheosh’s picture

I forgot to mention, this patch was applied to core before I tried using drush
http://drupal.org/node/735120#comment-2779976
It was an essential patch for me.

moshe weitzman’s picture

Category: bug » support
Status: Active » Fixed

Whats fbr.email_hash? Thats in the errant query. That column is not core drupal. Please disable contrib modules and retry.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

timotheosh’s picture

Yes the issue was with Facebook for Drupal module, which is not a production worthy module. Problem went away after uninstalling the module from the site. Thanks!