-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DuckDB with backup on GCS #6006
Conversation
…-duckdb-replicator
bootQueries = append(bootQueries, | ||
"SET preserve_insertion_order TO false", | ||
fmt.Sprintf("SET temp_directory = %s", safeSQLString(tempDir)), | ||
fmt.Sprintf("SET secret_directory = %s", safeSQLString(filepath.Join(dataDir, ".duckdb", "secrets"))), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this interfere with external table storage or will it just be ignored?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. These queries are executed for every db file so setting secret_directory
is what is expected.
But there could be issues if all database share same tmp directory. May be for new removing temp_directory
seems to be a safe option.
More important was to set unique secret_directory
for each instance's database.
closes https://github.com/rilldata/rill-private-issues/issues/692
Some of the previous logic removed from existing driver logic.
.tmp
and.wal
files if they are bigger than a certain size. Even on main it no longer works because thetmp
andwal
actually gets built in the attached DBs and notmain
.enum
conversion feature. Not being used anywhere and not documented as well. Can be added in therduckdb
if use case comes again.tx
support in duckdb driver. We no longer need to block read queries while attaching detaching.