<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>LibreDB Studio — DuckDB posts</title><description>Posts about DuckDB from the LibreDB Studio blog.</description><link>https://libredb.org/blog/engine/duckdb/</link><language>en</language><atom:link href="https://libredb.org/blog/engine/duckdb/rss.xml" rel="self" type="application/rss+xml"/><item><title>DuckDB storage answers, sessions and slow queries do not exist</title><link>https://libredb.org/blog/duckdb-storage-panels-no-sessions/</link><guid isPermaLink="true">https://libredb.org/blog/duckdb-storage-panels-no-sessions/</guid><description>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.</description><pubDate>Thu, 23 Jul 2026 09:00:00 GMT</pubDate><dc:creator>LibreDB</dc:creator><category>DuckDB</category><category>Engineering</category><category>Databases</category></item><item><title>One DuckDB file admits one process, readers included</title><link>https://libredb.org/blog/duckdb-single-process-file-lock/</link><guid isPermaLink="true">https://libredb.org/blog/duckdb-single-process-file-lock/</guid><description>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.</description><pubDate>Mon, 22 Jun 2026 09:00:00 GMT</pubDate><dc:creator>LibreDB</dc:creator><category>DuckDB</category><category>Engineering</category><category>Databases</category></item><item><title>Querying Parquet and CSV from the DuckDB editor</title><link>https://libredb.org/blog/duckdb-parquet-csv-editor-versus-agent/</link><guid isPermaLink="true">https://libredb.org/blog/duckdb-parquet-csv-editor-versus-agent/</guid><description>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.</description><pubDate>Sat, 09 May 2026 09:00:00 GMT</pubDate><dc:creator>LibreDB</dc:creator><category>DuckDB</category><category>Engineering</category><category>Databases</category></item><item><title>DuckDB plans are estimates here, permanently</title><link>https://libredb.org/blog/duckdb-explain-estimates-only/</link><guid isPermaLink="true">https://libredb.org/blog/duckdb-explain-estimates-only/</guid><description>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.</description><pubDate>Mon, 23 Mar 2026 09:00:00 GMT</pubDate><dc:creator>LibreDB</dc:creator><category>DuckDB</category><category>Engineering</category><category>Databases</category></item><item><title>DuckDB diagrams are scoped to the catalog you opened</title><link>https://libredb.org/blog/duckdb-er-diagram-current-database-scope/</link><guid isPermaLink="true">https://libredb.org/blog/duckdb-er-diagram-current-database-scope/</guid><description>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.</description><pubDate>Tue, 03 Feb 2026 09:00:00 GMT</pubDate><dc:creator>LibreDB</dc:creator><category>DuckDB</category><category>Engineering</category><category>Databases</category></item><item><title>Read-only mode is not the DuckDB boundary, external access is</title><link>https://libredb.org/blog/duckdb-agent-external-access-boundary/</link><guid isPermaLink="true">https://libredb.org/blog/duckdb-agent-external-access-boundary/</guid><description>Under read-only access alone, file copies, exports, extension installs and filesystem reads all succeeded while an insert was refused in the same session.</description><pubDate>Thu, 18 Dec 2025 09:00:00 GMT</pubDate><dc:creator>LibreDB</dc:creator><category>DuckDB</category><category>Engineering</category><category>Databases</category><category>Security</category></item></channel></rss>