Re: pg_restore hangs on materialized view [SEC=UNCLASSIFIED]

Is it possible that the reason the view is taking so long to build that
there is one or more relevant indexes in one of the source tables that
hasn't been built? That could slow down the creation of the view.

You could try commenting out the code that creates the view, using that to
create the rest of the DB and then add the view.

On Fri, Jun 22, 2018 at 4:47 AM, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:

> rohan(dot)parkes(at)dpc(dot)vic(dot)gov(dot)au wrote:
> > I have made a backup of a database using the pgAdmin backup command.
> Attempting to
> > restore it to a different server using the pgAdmin restore command
> results in the
> > process hanging.
> >
> > I tried using the pg_restore utility in order to get a better output of
> the restore process.
> > The restore gets to a particular materialized view and then just hangs.
> There's no kind
> > of error message, so I don't know what is causing the problem. I have
> checked the view
> > on the original server and it seems fine.
> >
> > At the moment all I can think to do is to try to exclude the
> materialized views from
> > the dump file and recreate them manually.
>
> Can you tell us the definition of the materialized view and the objects its
> query is using? Odds are that it is just taking a long time to build.
> Is it defined on a foreign table or something similar?
>
> Yours,
> Laurenz Albe
> Yours
> --
> Cybertec | https://www.cybertec-postgresql.com
>
> > Please consider the environment before printing this email
>
> Please consider the environment before wasting precious electrons.
>
>