]> git.ipfire.org Git - thirdparty/postgresql.git/commit
doc: Clarify inherited constraint behavior
authorAndrew Dunstan <andrew@dunslane.net>
Sat, 27 Jun 2026 21:43:02 +0000 (17:43 -0400)
committerAndrew Dunstan <andrew@dunslane.net>
Sat, 27 Jun 2026 21:51:26 +0000 (17:51 -0400)
commitd16be8605f5f699020fe4e6eaef008a41407a9bb
treeea67504977f99ab5c45b7823f284e506f7eabf41
parent0cd17fdd3c000f6e64e79da0fea5e65dc9f562df
doc: Clarify inherited constraint behavior

Update the table inheritance documentation to mention not-null constraints
alongside check constraints where inherited constraints are discussed.

Also clarify that some properties of inherited constraints can now be altered
directly on child tables, while the resulting constraint must remain compatible
with its inherited parent constraints.  For multiple inheritance, say explicitly
that when a column or constraint is inherited from more than one parent, the
stricter definition applies.

Author: Chao Li <lic@highgo.com>
Reviewed-by: Zsolt Parragi <zsolt.parragi@percona.com>
Discussion: https://postgr.es/m/E74C57FA-1DD0-4C8E-8FB1-538034752592@gmail.com
doc/src/sgml/ddl.sgml