Skip to content
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

Open
haubourg opened this issue Oct 28, 2016 · 5 comments
Open

restoring sample db fails to materialize network_segment view #28

haubourg opened this issue Oct 28, 2016 · 5 comments
Assignees

Comments

@haubourg
Copy link

usr/bin/pg_restore --host localhost --port 5432 --username "postgres" --dbname "qgep" --no-password "/home/regis/OSLANDIA/projets_locaux/QGEP/data-demodata/qgep_demodata.backup"

returns following errors:

pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 7468; 0 23690 MATERIALIZED VIEW DATA vw_network_segment postgres
pg_restore: [archiver (db)] could not execute query: ERROR:  function st_curvetoline(public.geometry, integer) does not exist
LINE 1: SELECT ST_CurveToLine($1, 32)
               ^
HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
QUERY:  SELECT ST_CurveToLine($1, 32)
CONTEXT:  SQL function "st_curvetoline" during inlining
    Command was: REFRESH MATERIALIZED VIEW vw_network_segment;

I suppose that this is a pg_restore error replacing $1 variable by 'public.geometry' when it should be 'geometry'

@tudorbarascu
Copy link
Contributor

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.

@sjib
Copy link
Contributor

sjib commented Jan 16, 2017

When importing the demo project the materialized view vw_network_segment has to be reinstalled manually - make update of the doku (@sjib)

@sjib
Copy link
Contributor

sjib commented Jan 16, 2017

Check with postgres developers why that view is not exported (@m-kuhn)

@sjib sjib assigned m-kuhn and sjib Jan 16, 2017
@sjib
Copy link
Contributor

sjib commented Nov 21, 2017

Add hint to doku - to do myself

@sjib
Copy link
Contributor

sjib commented Mar 30, 2019

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
If there is Code 1 but the schema is created and tables are created, just update materialized view - see #409

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants