-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
restoring sample db fails to materialize network_segment view #28
Comments
I can also replicate. Actually I noticed this some time ago but I got used on doing a refresh materialized view manually so it didn't bother me. Thanks for raising this. |
When importing the demo project the materialized view vw_network_segment has to be reinstalled manually - make update of the doku (@sjib) |
Check with postgres developers why that view is not exported (@m-kuhn) |
Add hint to doku - to do myself |
If you have problems with restore (Code 1 instead of 0 and have a message about wrong header) update to latest version of postgres - see also https://stackoverflow.com/questions/49064209/getting-archiver-unsupported-version-1-13-in-file-header-when-running-pg-r |
returns following errors:
I suppose that this is a pg_restore error replacing $1 variable by 'public.geometry' when it should be 'geometry'
The text was updated successfully, but these errors were encountered: