`DatabaseStore` crashes on PostgreSQL with `OperationalError: string too long to represent as jsonb string`

[adamchainz]

On a page with many database queries, the DatabaseStore managed to trigger:

File "/.../.venv/lib/python3.13/site-packages/django/db/backends/utils.py", line 105, in _execute
  return self.cursor. execute(sql, params)
File "/.../.venv/lib/python3.13/site-packages/psycopg/cursor.py", line 97, in execute
  raise ex.with_traceback(None)
django.db.utils.OperationalError: string too long to represent as jsonb string
LINE 1: UPDATE "debug_toolbar_historyentry" SET "data" = E'{"CacheP...

DETAIL: Due to an implementation restriction, jsonb strings cannot exceed 268435455 bytes.

It seems that the design of storing everything in one JSON field will need to follow this restriction, perhaps through chunking or making the data structure smarter

Alternatively, and possibly more fittingly, avoid using JSONField. If the JSON data doesn't need deconstructing within the database for queries, it's better to store JSON data in a text field. This can be any size and then loaded in Python only. The data can also then be compressed with zlib in the database, to save disk space and make writes and reads faster. (Django-MySQL's cache backend does this, for example.)

[adamchainz]

After a quick check in the code, particularly store.py, it seems the data within HistoryEntry.data is never queried: https://github.com/django-commons/django-debug-toolbar/blob/321d07dfd50054834eb8d47eabee708dcc716d7b/debug_toolbar/store.py . So I think migrating away from JSONField would make sense.