DuckDB storage answers, sessions and slow queries do not exist
Two catalog functions other engines have are absent here, so both panels stay empty carrying the engine own error, and table bytes are block-granular.
6 posts
Writing on DuckDB
In-process analytics — query Parquet and CSV files directly, with full EXPLAIN support and agent mode. Where it stops: Single-writer by design: no sessions to list, so health shows storage, not connections.
One DuckDB file admits one process, readers included
A second read-only process is refused with the same lock error as a second writer, which makes two Studio replicas on one file a broken configuration.
Querying Parquet and CSV from the DuckDB editor
File-reaching SQL works on the writable editor connection and is refused under the read-only agent handle, so the capability has to be stated with that split.
DuckDB plans are estimates here, permanently
The timing form of EXPLAIN executes the statement it was asked to explain, so it is never emitted and no measured node timings are published.
DuckDB diagrams are scoped to the catalog you opened
Foreign keys come from a single bulk read of the constraint catalog, and every catalog statement the DuckDB provider issues is scoped to the current database.
Read-only mode is not the DuckDB boundary, external access is
Under read-only access alone, file copies, exports, extension installs and filesystem reads all succeeded while an insert was refused in the same session.