From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Mark Hills <mark(at)xwax(dot)org> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Regression on pg_restore to 16.0: DOMAIN not available to SQL function |
Date: | 2023-11-03 14:19:26 |
Message-ID: | CAKFQuwaHjBv_u2t9YMftFiUPoLhphh8GepFGz1r_ttd82CkeQA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Friday, November 3, 2023, Mark Hills <mark(at)xwax(dot)org> wrote:
>
> pg_restore: error: could not execute query: ERROR: type "hash" does not
> exist
> LINE 7: )::hash;
> [...]
> CONTEXT: SQL function "gen_hash" during inlining
>
> --
> -- Relevant SQL declarations
> --
>
Those were not all of the relevant SQL declarations. In particular you
haven’t shown where in your schema the gen_hash gets called.
Odds are you’ve violated a “cannot execute queries in …” rule in something
like a generated column or a check expression. That it didn’t fail before
now is just a fluke.
I seem to recall another recent report of this for v16 that goes into more
detail.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Berg | 2023-11-03 14:26:05 | Re: meson documentation build open issues |
Previous Message | Ashutosh Bapat | 2023-11-03 14:01:14 | Re: RFC: Logging plan of the running query |