Error database foreman (PG::InternalError: ERROR: missing chunk number 0 for toast value 3180630 in pg_toast_2619)

Support
1

Problem:
d769777a | /usr/share/gems/gems/logging-2.3.1/lib/logging/diagnostic_context.rb:474:in block in create_with_logging_context' 2023-06-30T14:27:09 [I|app|d769777a] Rendered api/v2/errors/standard_error.json.rabl within api/v2/layouts/error_layout (Duration: 4.8ms | Allocations: 6392) 2023-06-30T14:27:09 [I|app|d769777a] Rendered layout api/v2/layouts/error_layout.json.erb (Duration: 8.0ms | Allocations: 12654) 2023-06-30T14:27:09 [I|app|d769777a] Completed 500 Internal Server Error in 125ms (Views: 8.4ms | ActiveRecord: 8.9ms | Allocations: 19086) 2023-06-30T14:27:09 [F|app|d769777a] **d769777a | ActiveRecord::StatementInvalid (PG::InternalError: ERROR: missing chunk number 0 for toast value 3180630 in pg_toast_2619** d769777a | ): d769777a | d769777a | lib/foreman/silenced_logger.rb:37:in silence’
d769777a | lib/foreman/silenced_logger.rb:37:in silence' d769777a | lib/foreman/middleware/logging_context_request.rb:11:in call’
d769777a | katello (4.8.1) lib/katello/prevent_json_parsing.rb:12:in `call’
Expected outcome:

Foreman and Proxy versions:

Foreman and Proxy plugin versions:

Distribution and version:

Other relevant data:

2

I can unlock trouble with a temporatry table.

But now this error below comeback again and again.

2023-07-07 18:25:11 CEST ERROR:  missing chunk number 0 for toast value 3180630 in pg_toast_2619
2023-07-07 18:25:11 CEST CONTEXT:  automatic analyze of table "foreman.public.sessions"
3

I’ll drop this table and recreate it.