Skip to content

Conversation

carlopi
Copy link
Contributor

@carlopi carlopi commented Sep 9, 2025

Example, you can attach a given ducklake in read/write mode like:

ATTACH 'ducklake:postgres:<CONNECTION_STRING>' AS my_ducklake (DATA_PATH 's3://some_bucket', STATIC_BACKUP 's3://some_bucket/backup.ducklake');
--- some operations
CALL ducklake_static_backup('my_ducklake');
--- this will copy metadata to a duckdb file at s3://some_bucket/backup.ducklake
--- some more operations
CALL ducklake_static_backup('my_ducklake');

And at the same time, a fully static read-only backup will be accessible like:

ATTACH 'ducklake:s3://some_bucket/backup.ducklake' (READ_ONLY); ---- DATA_PATH will be the same as the main ducklake instance

(note that backup will be up to date to the most recent ducklake_static_backup call that happened BEFORE attaching it)

Example, you can attach a given ducklake in read/write mode like:
```sql
ATTACH 'ducklake:postgres:<CONNECTION_STRING>' AS my_ducklake (DATA_PATH 's3://some_bucket', STATIC_BACKUP 's3://some_bucket/backup.ducklake');
--- some operations
CALL ducklake_static_backup('my_ducklake');
--- this will copy metadata to s3://some_bucket/backup.ducklake
```
And at the same time, a fully static backup will be accessible like:
```sql
ATTACH 'ducklake:s3://some_bucket/backup.ducklake' (READ_ONLY);
```
(note that backup will be up to date to the most recent `ducklake_static_backup` call that happened BEFORE attaching it)
@carlopi carlopi force-pushed the ducklake_static_backup branch from 9d456af to 524bff5 Compare September 9, 2025 07:24
@carlopi carlopi requested a review from pdet September 9, 2025 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant