I was able to get this to work eventually, but in our case (same team as tfwright above) we had to delete a whole lot of stuff to get the import to work:
pg_similiarity, postgis, tiger, topology, spatial_ref_sys
There were also many blocks of this sort:
REVOKE ALL ON TABLE public.geometry_columns FROM postgres;
REVOKE SELECT ON TABLE public.geometry_columns FROM PUBLIC;
GRANT ALL ON TABLE public.geometry_columns TO our_app_s76r_user;
GRANT SELECT ON TABLE public.geometry_columns TO PUBLIC;
In which case I replaced our_app_s76r_user with the postgres username for our local database. Alternatively I imagine you could just delete all the revoke/grant sections, I imagine, but that was more work than a search and replace on the name.
I am not sure if it is specific to Ecto (Elixir’s database wrapper), but in our case we couldn’t just ignore the errors, they actually halt the import. Had to fix all of the above in order for it to succeed.
I wonder if, moving forward, Render might be able to provide an option for an export that doesn’t include all of this stuff, or if there is a way to exclude it via the pg_dump command perhaps because otherwise I think we’re looking at writing a script to strip all of this stuff out. Thoughts?