From: | Nicola Contu <nicola(dot)contu(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-general(at)lists(dot)postgresql(dot)org, Alessandro Aste <Alessandro(dot)aste(at)gtt(dot)net> |
Subject: | Re: Restore from dumps |
Date: | 2018-07-25 14:33:25 |
Message-ID: | CAMTZZh2xTRbyrqC8x0E8Mt5-FgARxKYPveH9Oq3-wx_XKUPHUQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
yeah, we updated that function in production to says public.all_days.
I will let you know at the next restore.
Thanks guys, appreciated.
2018-07-25 16:28 GMT+02:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> > Nicola Contu wrote:
> >> pg_restore: [archiver (db)] could not execute query: ERROR: relation
> "all_days" does not exist
> >> LINE 3: from all_days
> >> ^
> >> QUERY:
> >> select count(*)::numeric
> >> from all_days
> >> where (("date" between $2::date and $1::date) or ("date" between
> $1::date and $2::date))
> >> and dow not in (0,6)
> >>
> >> CONTEXT: SQL function "bdays" during inlining
>
> > Try to ALTER the materialized view so that it refers to "public.all_days"
> > rather than "all_days".
>
> Per the error message, what needs fixing is the SQL function "bdays",
> not the matview as such.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2018-07-25 15:15:56 | Order in which tables are dumped |
Previous Message | Tom Lane | 2018-07-25 14:28:45 | Re: Restore from dumps |