From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: pg_restore and materialized view deps |
Date: | 2024-09-07 01:41:22 |
Message-ID: | CAOC+FBWOTSi3DXHBjWdBrVpYOKTrf+aQ5N32BMDwJM3uKgfGXw@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ah, you know, a little deeper: it's an issue with a mat view unable to
refresh because it uses a function, and within that function, there is a
call to a mat view not yet materialized.
On Fri, Sep 6, 2024 at 6:33 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Wells Oliver <wells(dot)oliver(at)gmail(dot)com> writes:
> > Not the end of the world but I notice when running pg_restore that I
> > encounter a few errors where materialized views cannot be refreshed
> because
> > they query other materialized views not yet refreshed.
>
> Oh? There are dependencies that are supposed to prevent that.
> Can you provide a self-contained example of a schema where
> that doesn't work?
>
> regards, tom lane
>
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-09-07 02:12:34 | Re: pg_restore and materialized view deps |
Previous Message | Tom Lane | 2024-09-07 01:33:01 | Re: pg_restore and materialized view deps |