Skip to content
This repository was archived by the owner on Oct 10, 2025. It is now read-only.

Commit 789dd4c

Browse files
authored
Document the behaviour of import/export database with indexes (#340)
1 parent ca49c2f commit 789dd4c

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

src/content/docs/migrate/index.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,10 @@ For more compact storage, you can export the data files in Parquet format as fol
3434
EXPORT DATABASE '/path/to/export' (format="parquet");
3535
```
3636

37+
:::note[Note]
38+
The EXPORT DATABASE command also exports all indexes, regardless of whether their dependent extensions have been loaded or not.
39+
:::
40+
3741
## Import database
3842

3943
The `IMPORT DATABASE` command imports the contents of the database from a specific directory to which
@@ -48,8 +52,9 @@ IMPORT DATABASE '/path/to/export';
4852
```
4953

5054
:::note[Note]
51-
The `IMPORT DATABASE` command can only be executed on an empty database.
55+
1. The `IMPORT DATABASE` command can only be executed on an empty database.
5256
Currently, in case of a failure during the execution of the `IMPORT DATABASE` command,
5357
automatic rollback is not supported. Therefore, if the `IMPORT DATABASE` command fails, you will need to delete the
5458
database directory you are connected to and reload it again.
59+
2. The `IMPORT DATABASE` command also imports all indexes, regardless of whether their dependent extensions were loaded during export. If an index's dependent extension was loaded at the time of export, it will be automatically loaded during import. However, if the dependent extension was not loaded during export, it will not be automatically loaded during import. In such cases, users must manually load the dependent extensions before querying the index.
5560
:::

0 commit comments

Comments
 (0)