I have noticed that in my postgres logs duplicate key errors:

024-05-05 14:19:32.241 AEST [1833639] ERROR:  duplicate key value violates unique constraint "uq_block_schema__checksum_version"
2024-05-05 14:19:32.241 AEST [1833639] DETAIL:  Key (checksum, version)=(sha256:6db1ab242e7b2b88a52dc137a7da3a373af63e0a103b9a91e060ed54a26f395a, 2.
18.3) already exists.
2024-05-05 14:19:32.241 AEST [1833639] STATEMENT:  INSERT INTO block_schema (checksum, fields, capabilities, version, block_type_id, id, created, up
dated) VALUES ($1::VARCHAR, $2::JSONB, $3::JSONB, $4::VARCHAR, $5::UUID, $6::UUID, $7::TIMESTAMP WITH TIME ZONE, $8::TIMESTAMP WITH TIME ZONE)
2024-05-05 14:20:27.300 AEST [1825227] LOG:  checkpoint starting: time
2024-05-05 14:21:27.128 AEST [1825227] LOG:  checkpoint complete: wrote 61257 buffers (1.0%); 0 WAL file(s) added, 0 removed, 24 recycled; write=59.
780 s, sync=0.027 s, total=59.828 s; sync files=134, longest=0.007 s, average=0.001 s; distance=398495 kB, estimate=470706 kB; lsn=1CB/1E55DA58, red
o lsn=1CB/9C5610

This database is only supporting prefect, and I am not sure if the duplicate key is a result of postgres somehow, or if there is something on the prefect side that might be at play. I only bothered looking at this after I was not able to load some of my markdown artefacts that I registed within some prefect tasks. They should load a png image in the UI, but instead kind of hung. The raw markdown string seemed to be present though. The image would never load though. Not a huge deal, just interested in thisn and completely unsure if they are related.