pgsql: Clarify comment about temporal foreign keys

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Clarify comment about temporal foreign keys
Date: 2025-12-13 15:52:21
Message-ID: E1vURuu-000XzA-0n@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Clarify comment about temporal foreign keys

In RI_ConstraintInfo, period_contained_by_oper and
period_intersect_oper can take either anyrange or anymultirange.

Author: Paul A. Jungwirth <pj(at)illuminatedcomputing(dot)com>
Discussion: https://www.postgresql.org/message-id/CA%2BrenyWzDth%2BjqLZA2L2Cezs3wE%2BWX-5P8W2EOVx_zfFD%3Daicg%40mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/ff30bad7f6f085598e61bb06a8433cb33b3400c7

Modified Files
--------------
src/backend/utils/adt/ri_triggers.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2025-12-13 15:57:03 pgsql: Fix out-of-date comment on makeRangeConstructors
Previous Message Álvaro Herrera 2025-12-12 13:27:06 pgsql: Reject opclass options in ON CONFLICT clause