Rahul_Goswami encountered a database error after upgrading Discourse to stable version 2.7.7, specifically a PostgreSQL error: function max(boolean) does not exist, which occurred during account activation Rahul_Goswami. pfaffman advised checking for non-standard plugins and rebuilding from the command line. Rahul confirmed upgrading via SSH and shared his app.ymlRahul_Goswami, noting no non-standard plugins. Falco clarified that switching from tests-passed to stable directly is invalid — the version should be reset to default and rebuilt. pfaffman reiterated that switching to stable doesn’t fix underlying upgrade failures and urged reverting to tests-passed and diagnosing the root cause. After rebuilding without the version: stable line, Rahul’s site went down again, with logs showing further errors Rahul_Goswami. pfaffman then suggested removing the discourse-tagging plugin, which is redundant in modern Discourse versions. Following this advice, Rahul confirmed the issue was resolved Rahul_Goswami. The core issue stemmed from an outdated or incompatible plugin and improper version handling during upgrade.
Failed to handle exception in exception app middleware : PG::UndefinedFunction: ERROR: function max(boolean) does not exist
LINE 1: …_rank, MAX(user_badges.created_at) AS created_at, MAX(user_b…
^
HINT: No function matches the given name and argument types. You might need to add explicit type casts.
Started GET “/users/activate-account/0f44cb2f759b85caecaf5ea26a1878e5” for 49.44.84.137 at 2021-08-04 11:54:11 +0000
Processing by UsersController#activate_account as HTML
Parameters: {“token”=>“0f44cb2f759b85caecaf5ea26a1878e5”}
Rendered users/activate_account.html.erb within layouts/no_ember (Duration: 2.0ms | Allocations: 471)
Rendered layout layouts/no_ember.html.erb (Duration: 20.5ms | Allocations: 5694)
Completed 200 OK in 29ms (Views: 21.8ms | ActiveRecord: 0.0ms | Allocations: 7981)