I ran a delete from mytable (I have a requirement to leave the table in place) on a large table and got OOM on Pulse. I switched to Standard and tried again, but now get TransactionContext Error: Conflict on tuple deletion! Can you offer guidance?
Hey Greg, Looking into it!
Thanks Tia.
Which account and user are you getting this error ?
Our organization is Polygon Research; the user is atlas@polygonresearch.com. And, I just tried the delete again on Standard, and it worked this time. So my request morphs into: why did it happen the first time, and what guidance can you offer for this scenario going forward?
Thanks for the update, we are looking into what occurred and I'll let you know what we find!
Hi Greg O. Our logs show the initial delete hit an out-of-memory error before it could commit. Moving to Standard raised the memory limit but kept the same duckling running, so the retries failed on leftover state from that first attempt rather than on memory. It went through once you landed on a fresh duckling about an hour later. Going forward: and unqualified DELETE FROM holds deletion bookkeeping for every row in a single transaction, so chunking it with a commit per chunk, like you did in your later DML queries, keeps memory use flat not matter how large the table gets. If a write does fail, SHUTDOWN cycles the duckling before you retry, especially if you've upgraded the duckling size in between. docs here
H Isaac, thanks. One correction - I changed the Duckling size right away after the OOM. Does the GUI sometimes fail to reflect the transition accurately - i.e. mine failed to change (for an hour), but say it has?
HI Greg, Confirmed, the UI was showing your configured size, but the swap to a standard duckling hadn't happened yet. The running Duckling isn't replaced until it clears a window of inactivity. To force it to swap, you can run the SQL command SHUTDOWN or Reset Ducklings in the UI. That ends the current Duckling so the new size take effect on your next query instead of waiting on cooldown. The gap between the configured size and the Duckling actually running isn't visible anywhere today. I'll pass this along to our UI team and I'll follow up with you if anything changes.
Thanks Isaac.
Happy to help! Let us know if you anything else comes up.
.png)