| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Michał Tęcza <michal(dot)tecza(at)softiq(dot)pl> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_restore: error: could not execute query: ERROR: schema does not exist |
| Date: | 2026-05-08 14:41:56 |
| Message-ID: | CAHGQGwG=sm5McBMbEbkwrPz4uyy7DDDL8MwY7e0is_eJ_8gG-g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, May 8, 2026 at 1:30 PM Michał Tęcza <michal(dot)tecza(at)softiq(dot)pl> wrote:
>
> When restoring a database with some specific view, pg_restore produce an error - schema does not exists.
> This behavior was reproduced on latest version - 18.3
This issue was previously reported and discussed at [1]. As mentioned there,
the --if-exists option can suppress some "does not exist" errors,
but it does not guarantee that all such errors can be avoided.
Regards,
[1] https://postgr.es/m/b43e03eb-3997-700e-c2d4-92c31e4e31ee@dalibo.com
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2026-05-08 19:29:44 | BUG #19473: regression error in dblink: another command is already in progress |
| Previous Message | Richard Guo | 2026-05-08 08:35:27 | Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor> |