Greg O.

Commented on How to Resolve Out of Memory and TransactionContex...·Posted inHelp

Thanks Isaac.

Commented on How to Resolve Out of Memory and TransactionContex...·Posted inHelp

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?

Commented on How to Resolve Out of Memory and TransactionContex...·Posted inHelp

Greg O.

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?

Commented on How to Resolve Out of Memory and TransactionContex...·Posted inHelp

Greg O.

Thanks Tia.

Posted in Help·

Greg O.

How to Resolve Out of Memory and TransactionContext Errors When Deleting Large Table Data in Snowflake

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?

10Comments

Commented on Does MotherDuck’s seven-day failsafe preserve dele...·Posted inHelp

Greg O.

Terrific - thanks Noah.

Commented on Does MotherDuck’s seven-day failsafe preserve dele...·Posted inHelp

Greg O.

Thanks. This confirms the bucket-lock behavior we needed. One final operational clarification: the ALTER DATABASE SET SNAPSHOT documentation says DuckLake databases do not support snapshot restore. For a MotherDuck-managed BYOB DuckLake, what exact procedure restores its metadata catalog to a snapshot shown in MD_INFORMATION_SCHEMA.DATABASE_SNAPSHOTS? Is this support-assisted, and can we request an exact SNAPSHOT_ID? During recovery, should we restore the corresponding R2 backup first and keep bucket lock enabled until the restored files_scheduled_for_deletion queue has been reviewed?

Commented on Does MotherDuck’s seven-day failsafe preserve dele...·Posted inHelp

Greg O.

Thanks—that confirms the seven-day failsafe is metadata-only. For a MotherDuck-hosted DuckLake catalog with BYOB R2:

1.
If we request recovery within seven days to immediately before a ducklake_expire_snapshots operation, will the restored catalog also restore the snapshot and files_scheduled_for_deletion state, provided the R2 objects have not yet been cleaned up?
2.
What is the supported way to export or back up __ducklake_metadata_<database> so it can be paired with our own R2 object backup and used in a tested disaster-recovery procedure?If R2 rejects DeleteObject because of a bucket-lock rule, does ducklake_cleanup_old_files leave the file scheduled and safely retryable without removing its metadata record?

Posted in Help·

Greg O.

Is there a solution when Cancel doesn't work on a long-runnign query?

1 attachment

1Comment

Posted in Help·

Greg O.

Does MotherDuck’s seven-day failsafe preserve deleted R2 Parquet files or only catalog metadata in BYOB DuckLake?

Hi, for a BYOB DuckLake using R2, does ducklake_cleanup_old_files physically delete Parquet objects from our bucket? And does MotherDuck’s seven-day failsafe actually preserve or allow recovery of those deleted R2 objects—or does it protect only the catalog metadata?

8Comments

About

Start Date
Title