You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@amarshall unfortunately, I don't have the exact output, but I can specify the reason:
Since heroku doesn't give its users superuser access to their postgres instances, it's impossible for someone to run a CREATE OR REPLACE PROCEDURAL LANGUAGE command via psql. The function in function.rb will abort at the first line of the SQL setup.
My workaround was to remove the line, as there's no need to ensure plpgsql is present, because it is by default on 9.3.
One solution would be wrapping this line in a BEGIN; EXCEPTION; block. Another would be to remove the line entirely, which would drop support for postgres 8.x versions (seems a bit heavy handed). Thoughts?
Activity
amarshall commentedon Nov 18, 2014
For reference, what’s the exact error you get?
danielgrippi commentedon Nov 30, 2014
@amarshall unfortunately, I don't have the exact output, but I can specify the reason:
Since heroku doesn't give its users superuser access to their postgres instances, it's impossible for someone to run a
CREATE OR REPLACE PROCEDURAL LANGUAGEcommand via psql. The function infunction.rbwill abort at the first line of the SQL setup.My workaround was to remove the line, as there's no need to ensure
plpgsqlis present, because it is by default on 9.3.One solution would be wrapping this line in a
BEGIN; EXCEPTION;block. Another would be to remove the line entirely, which would drop support for postgres 8.x versions (seems a bit heavy handed). Thoughts?Remove create plpgsql language line. This wont work on heroku - see C…