|
|
|
|
@ -182,6 +182,29 @@ Branch: REL_16_STABLE [ec20a4552] 2026-02-20 18:04:26 +0900 |
|
|
|
|
|
|
|
|
|
<listitem> |
|
|
|
|
<!-- |
|
|
|
|
Author: Álvaro Herrera <alvherre@kurilemu.de> |
|
|
|
|
Branch: master [0eeffd31b] 2026-02-21 12:22:08 +0100 |
|
|
|
|
Branch: REL_18_STABLE [8d9a97e0b] 2026-02-21 12:22:08 +0100 |
|
|
|
|
--> |
|
|
|
|
<para> |
|
|
|
|
Avoid name collisions between user-written constraints and |
|
|
|
|
automatically-named <literal>NOT NULL</literal> constraints |
|
|
|
|
(Laurenz Albe) |
|
|
|
|
<ulink url="&commit_baseurl;8d9a97e0b">§</ulink> |
|
|
|
|
</para> |
|
|
|
|
|
|
|
|
|
<para> |
|
|
|
|
As of version 18, <literal>NOT NULL</literal> constraints have |
|
|
|
|
full-fledged <structname>pg_constraint</structname> entries, and |
|
|
|
|
therefore require names. The logic for choosing a name for an |
|
|
|
|
unnamed <literal>NOT NULL</literal> constraint failed to avoid |
|
|
|
|
conflicts with user-written constraints elsewhere in the |
|
|
|
|
same <command>CREATE TABLE</command> statement. |
|
|
|
|
</para> |
|
|
|
|
</listitem> |
|
|
|
|
|
|
|
|
|
<listitem> |
|
|
|
|
<!-- |
|
|
|
|
Author: Heikki Linnakangas <heikki.linnakangas@iki.fi> |
|
|
|
|
Branch: master [78a5e3074] 2026-02-11 18:50:57 +0200 |
|
|
|
|
Branch: REL_18_STABLE [53463b4b2] 2026-02-11 18:51:06 +0200 |
|
|
|
|
|