Doc limitation update proposal: include out-of-line OID usage per TOAST-ed columns

Jakub Wartak <jakub.wartak@enterprisedb.com>

From: Jakub Wartak <jakub.wartak@enterprisedb.com>

To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2023-04-21T06:39:10Z

Lists: pgsql-hackers

Hi -hackers,

I would like to ask if it wouldn't be good idea to copy the
https://wiki.postgresql.org/wiki/TOAST#Total_table_size_limit
discussion (out-of-line OID usage per TOAST-ed columns / potential
limitation) to the official "Appendix K. PostgreSQL Limits" with also
little bonus mentioning the "still searching for an unused OID in
relation" notice. Although it is pretty obvious information for some
and from commit 7fbcee1b2d5f1012c67942126881bd492e95077e and the
discussion in [1], I wonder if the information shouldn't be a little
more well known via the limitation (especially to steer people away
from designing very wide non-partitioned tables).

Regards,
-J.

[1] - https://www.postgresql.org/message-id/flat/16722-93043fb459a41073%40postgresql.org

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Document limit on the number of out-of-line values per table
- e51160fa0bab 15.9 landed
- dda341b32c88 14.14 landed
- c9aa6f4f86fc 13.17 landed
- 667401dd40c8 17.0 landed
- 5ff394503ce2 12.21 landed
- 4d93bbd4e0d4 18.0 landed
- 409be33c3136 16.5 landed
Log when GetNewOidWithIndex() fails to find unused OID many times.
- 7fbcee1b2d5f 14.0 cited