Error coming from puppetdb and partitions?

[Dan Mahoney]

Hey there folks,

We're using puppetdb and we see this error fairly regularly in our logs.  Anyone have any ideas?  We're using puppet8 under FreeBSD, with postgres 17.  

2025-06-18T00:46:27+00:00 repo-us postgres [local0.warning] [7-1] 2025-06-18 00:46:27.415 UTC [93417] ERROR:  no partition of relation "reports_historical" found for row

2025-06-18T00:46:27+00:00 repo-us postgres [local0.warning] [7-2] 2025-06-18 00:46:27.415 UTC [93417] DETAIL:  Partition key of the failing row contains (producer_timestamp) = (2025-06-18 00:16:27.044+00).

2025-06-18T00:46:27+00:00 repo-us postgres [local0.warning] [7-3] 2025-06-18 00:46:27.415 UTC [93417] STATEMENT:  UPDATE reports SET latest = $1 WHERE latest = true and certname = $2

We don't have any reports_ttl set or anything like that, only a node_ttl which is at 365d.

Any other info that would help?

[Dan Mahoney]

Okay, no response at all so far.  Is there a better place to ask about this?

We've pushed an issue here: https://github.com/puppetlabs/puppetdb/issues/4020

-Dan