We're getting the following warnings every day from a clean PuppetDB 8 installation with Postgres 17:
[local0.warning] [7-1] 2025-06-02 00:41:48.906 UTC [53444] ERROR: no partition of relation "reports_historical" found for row
[7-2] 2025-06-02 00:41:48.906 UTC [53444] DETAIL: Partition key of the failing row contains (producer_timestamp) = (2025-06-02 00:11:48.939+00).
[local0.warning] [7-3] 2025-06-02 00:41:48.906 UTC [53444] STATEMENT: UPDATE reports SET latest = $1 WHERE latest = true and certname = $2
Should I be concerned about them, or is there a simple schema fix to resolve them?
We're getting the following warnings every day from a clean PuppetDB 8 installation with Postgres 17:
Should I be concerned about them, or is there a simple schema fix to resolve them?