From d97a60b7e56c57a242668609c8fb82e6a6a32506 Mon Sep 17 00:00:00 2001 From: "Paul A. Jungwirth" Date: Wed, 8 May 2024 20:41:05 -0700 Subject: [PATCH] Reword docs for temporal PKs with implicit referent The old docs had confusing language about "one side" of the foreign key, which could mean either the referenced primary key itself or the REFERENCES clause of the FK declaration. Author: David G. Johnston Discussion: https://www.postgresql.org/message-id/ZjpApuq8I9DE5Elv%40momjian.us --- doc/src/sgml/ref/create_table.sgml | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 02f31d2d6fd..75f06bc49cc 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -1184,11 +1184,13 @@ WITH ( MODULUS numeric_literal, REM referent for its entire duration. This column must be a range or multirange type. In addition, the referenced table must have a primary key or unique constraint declared with WITHOUT - OVERLAPS. Finally, if one side of the foreign key uses - PERIOD, the other side must too. If the refcolumn list is omitted, the - WITHOUT OVERLAPS part of the primary key is treated - as if marked with PERIOD. + OVERLAPS. Finally, if the foreign key has a PERIOD + column_name specification + the corresponding refcolumn, + if present, must also be marked PERIOD. If the + refcolumn clause is omitted, + and thus the reftable's primary key constraint chosen, the primary key + must have its final column marked WITHOUT OVERLAPS. -- 2.42.0