pgsql: Enforce pg_class.relchecks limit (32,767 or INT16_MAX) - Mailing list pgsql-committers

From Michael Paquier
Subject pgsql: Enforce pg_class.relchecks limit (32,767 or INT16_MAX)
Date
Msg-id E1xAwqQ-00000001WC9-3TH0@gemulon.postgresql.org
Whole thread
List pgsql-committers
Enforce pg_class.relchecks limit (32,767 or INT16_MAX)

pg_class.relchecks reports the number of CHECK constraints in a table,
and is stored within a smallint.  It was possible to define a table that
could overflow the counter when specifying more than 32k constraints
(new table or adding a constraint).  This would cause the table to
become undroppable, as this counter should never be negative when
dropping these constraints.

Author: Matthias van de Meent <boekewurm+postgres@gmail.com>
Reviewed-by: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Reviewed-by: Jian He <jian.universality@gmail.com>
Reviewed-by: Sivaprasad <sivaprasad.postgres@gmail.com>
Discussion: https://postgr.es/m/CAEze2WjSW4qaHYnvkTtbknp85eGEirGJTLMZatotdJJKiA+_hA@mail.gmail.com
Backpatch-through: 14

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/5e59290402518db5b2876ecd627c7d79f73eaa44

Modified Files
--------------
doc/src/sgml/limits.sgml   |  7 +++++++
src/backend/catalog/heap.c | 28 +++++++++++++++++++++++-----
2 files changed, 30 insertions(+), 5 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Don't emit garbage "\[un]restrict (null)" commands in pg_dump.
Next
From: Michael Paquier
Date:
Subject: pgsql: Refactor assembly of external on-disk TOAST pointers