Re: NOT ENFORCED constraint feature

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: Amul Sul <sulamul(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Joel Jacobson <joel(at)compiler(dot)org>, Alexandra Wang <alexandra(dot)wang(dot)oss(at)gmail(dot)com>, Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>
Subject: Re: NOT ENFORCED constraint feature
Date: 2025-03-28 10:03:51
Message-ID: CAExHW5tM4NkSPeDMP5hRsh0u6LYgOZMa7W-et2nCQ4gz9cWrNw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 27, 2025 at 6:25 PM Amul Sul <sulamul(at)gmail(dot)com> wrote:

>
> I am not sure how to make such tests stable enough since the trigger
> name involves OIDs. In count check, I tried adjusting the join
> condition to ensure that I get the exact same type of constraint
> w.r.t. trigger relation and the constraint.

There are tests which mask variable parts of EXPLAIN output. Can we
use similar trick to mask OIDs from the trigger names?

--
Best Wishes,
Ashutosh Bapat

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Евгений Горбанев 2025-03-28 10:12:37 Re: Assert failure in base_yyparse
Previous Message Shlok Kyal 2025-03-28 09:43:44 Re: Restrict publishing of partitioned table with a foreign table as partition