Skip to content

asyncpg INSERT error #12269

Answered by robd003
robd003 asked this question in Q&A
Mar 29, 2022 · 1 comments · 2 replies
Discussion options

You must be logged in to vote

Turns out this was a side-effect when we did performance testing on this cluster and hit the high water mark on the disk.

I fixed it by running ALTER TABLE tablename SET ("blocks.read_only_allow_delete" = FALSE); on every single table which was annoying...

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@proddata
Comment options

@mfussenegger
Comment options

Answer selected by proddata
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants