Re: pg_dump/restore failure (dependency?) on BF serinus

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Subject: Re: pg_dump/restore failure (dependency?) on BF serinus
Date: 2025-04-08 04:11:55
Message-ID: 3885904.1744085515@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
>> # Running: pg_restore --create -j2 -d postgres /home/bf/bf-build/serinus/HEAD/pgsql.build/testrun/pg_upgrade/002_pg_upgrade/data/tmp_test_KTss/regression.dump
>> pg_restore: error: could not execute query: ERROR: there is no unique constraint matching given keys for referenced table "pk"
>> Command was: ALTER TABLE fkpart5.fk
>> ADD CONSTRAINT fk_a_fkey FOREIGN KEY (a) REFERENCES fkpart5.pk(a);

> It's hard to tell without more logging, but the most likely explanation for
> this seems that somehow the primary key on fkpart5.pk hasn't yet been
> restored. However, looking at the pg_restore -v -l of the regression test
> database locally, the relevant dependencies look sane on a first glance.

This feels quite adjacent to my complaint here:

https://www.postgresql.org/message-id/2045026.1743801143%40sss.pgh.pa.us

though perhaps it's not exactly the same. I plan to start looking
into a fix for that tomorrow.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2025-04-08 04:19:53 Re: pg_dump/restore failure (dependency?) on BF serinus
Previous Message Andres Freund 2025-04-08 03:41:34 pg_dump/restore failure (dependency?) on BF serinus