Re: BUG #19548: Missing dependency between a graph edge and the related PK

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Ayoub Kazar <kazarayoub2004(at)gmail(dot)com>, christophe(dot)courtois(at)dalibo(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19548: Missing dependency between a graph edge and the related PK
Date: 2026-07-17 14:25:18
Message-ID: fd4b8e54-f19f-4e4b-ba0c-0108ab7bc871@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 16.07.26 14:13, Ayoub Kazar wrote:
> I checked with Oracle as well to see the behavior and i can confirm its
> the same (its a standard thing, see below).
>
> The KEY, either explicit or implicit through the PK is used just at
> graph definition time: the catalog just keeps the column numbers in the
> relative graph element table (in your case, the family table). There's
> no dependency kept.

Correct. The current behavior is intentional.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Paul Kim 2026-07-17 14:28:47 Re: BUG #19523: psql tab-completion shadows pg_db_role_setting
Previous Message Matthias van de Meent 2026-07-17 10:22:27 Re: BUG #19519: REPACK can fail due to missing chunk for toast value