Hi, What appears to be a pg_dump/pg_restore bug was observed with the new BEGIN ATOMIC function body syntax introduced in Postgres 14.
Dependencies inside a BEGIN ATOMIC function cannot be resolved if those dependencies are dumped after the function body. The repro case is when a primary key constraint is used in a ON CONFLICT ON CONSTRAINT used within the function. With the attached repro, pg_restore fails with pg_restore: error: could not execute query: ERROR: constraint "a_pkey" for table "a" does not exist Command was: CREATE FUNCTION public.a_f(c1_in text, c2 integer DEFAULT 60) RETURNS void I am not sure if the answer if to dump functions later on in the process. Would appreciate some feedback on this issue. Regards, Sami Imseih Amazon Web Services (AWS)
repro.sh
Description: repro.sh
