The 1.0 release is finally here! A ton of features were added, and performance improved immensely, and of course lots of fixes... And that means pg_duckdb is now ready for production!

You can read the release blog on the MotherDuck website

Added

• Add support for converting Postgres table values in parallel. This can speed up large scans a lot. You can use duckdb.threads_for_postgres_scan to configure how many threads it should use. ([#762])
• Add support for statically compiling the duckdb library into the pg_duckdb extension. (#618)
• Add support for DOMAIN, VARINT, TIME, TIMETZ, BIT, VARBIT, UNION, MAP, STRUCT types. (#532, #626, #627, #628, #636, #678, #689, #669)
• Add support for installing community extensions. (#647)
• Add support for DDL on DuckDB tables in transactions. (#632)
• Make duckdb.unresolved_type support min, date_trunc, length, regexp_replace, LIKE, ILIKE, SIMILAR TO. (#643)
• Add cast from duckdb.unresolved_type to bytea and text. (#643, [#915])
• Add support for the DuckDB date/time functions: strftime, strptime, epoch, epoch_ms, epoch_us, epoch_ns, time_bucket, make_timestamp, make_timestamptz. (#643)
• Add support for using MotherDuck in multiple Postgres databases. (#544, #545)
• Add ALTER TABLE support for DuckDB tables. (#652)
• Add support to COPY ... TO and COPY ... FROM for DuckDB tables. (#665)
• Add support for EXPLAIN (FORMAT JSON) for DuckDB queries. ([#654])
• Add support for single dimension ARRAY types from DuckDB, before only LIST was supported. ([#655])
• Add support for TABLESAMPLE. ([#559])
• Add duckdb.extension_directory, duckdb.temporary_directory and duckdb.max_temporary_directory_size settings. ([#704])
• Add source locations to error messages. ([#758])
• Add basic collation support by allowing users to configure duckdb.default_collation. ([#814])
• Add support for MotherDuck views. You can now create views inside MotherDuck and query views that are already stored in MotherDuck. ([#822])
• Add support for Postgres 18 Release Candidate 1. Since Postgres 18 has not had a final release yet, this is still considered an experimental feature. ([#788])
• Add support for UUIDs in prepared statement arguments. ([#863])
• Add duckdb.azure_transport_option_type setting to configure Azure extension transport options, which can be used to workaround issue #882. ([#910])

Changed

• Update to DuckDB 1.3.2. ([#754], [#858])
• Change the way MotherDuck is configured. It's not done anymore through the Postgres configuration file. Instead, you should now enable MotherDuck using CALL duckdb.enable_motherduck(...) or equivalent CREATE SERVER and CREATE USER MAPPING commands. ([#668])
• Change the way secrets are added to DuckDB. You'll need to recreate your secrets using the new method duckdb.create_simple_secret or duckdb.create_azure_secret functions. Internally secrets are now stored SERVER and USER MAPPING for the duckdb foreign data wrapper. ([#697])
• Disallow DuckDB execution inside functions by default. This feature can cause crashes in rare cases and is intended to be re-enabled in a future release. For now you can use duckdb.unsafe_allow_execution_inside_function to allow functions anyway. ([#764], [#884])
• Don't convert Postgres NUMERICs with a precision that's unsupported in DuckDB to double by default. Instead it will throw an error. If you want the lossy conversion to DOUBLE to happen, you can enable duckdb.convert_unsupported_numeric_to_double. ([#795])
• Remove custom HTTP caching logic. ([#644])
• When creating a table in a ddb$ schema that table now uses the duckdb table access method by default. ([#650])
• Do not allow creating non-duckdb tables in a ddb$ schema. ([#650])
• When creating MotherDuck tables from Postgres, automatically make them be created by the table creation. Before you had to set the ROLE manually before issuing the CREATE TABLE command. ([#650])
• Add automated tests for MotherDuck integration. ([#649])
• Sync the Postgres timezone to DuckDB when initializing the DuckDB connection. This makes some date parsing/formatting behave better. (#643, [#853])
• Support FORMAT JSON for COPY commands. (#665)
• Force COPY to use DuckDB execution when using duckdb.force_execution. (#665)
• Automatically use DuckDB execution for COPY when file extensions are used for filetypes that DuckDB understands (.parquet, .json, .ndjson, jsonl, .gz, .zst). (#665)
• Automatically use DuckDB execution for COPY when copying from Azure and HTTP locations. ([#872])
• Return TEXT columns instead of VARCHAR columns when using DuckDB execution. ([#583])
• Extensions in duckdb.extensions now get automatically installed before running any DuckDB query if duckdb.autoinstall_known_extensions is set to true. This helps with read-replica setups, where the extension gets installed on the primary and but the replica is queried. ([#801])
• By default duckdb.disabled_filesystems is now empty. To keep the default installation secure, LocalFileSystem will now be appended for any user that does not have the pg_read_server_files and pg_write_server_files privileges. ([#802])
• Push down LIKE expressions and upper()/lower() calls to Postgres storage. These expressions can sometimes be pushed down to the index. ([#808])
• Changed duckdb.max_memory/duckdb.memory_limit to accept integer values instead of a string, to avoid users entering values that DuckDB does not understand. This breaks backwards compatibility slightly: MiB, GiB etc suffixes are now not supported anymore, only MB, GB etc suffixes are now allowed. ([#883])
• Add support for sub-extensions. This allows other Postgres extensions to build on top of pg_duckdb. ([#893])

Fixed

• Fix possible crash when querying two Postgres tables in the same query. ([#604])
• Fix crash when loading the postgres extension for DuckDB (a.k.a. postgres_scanner) into pg_duckdb ([#607])
• Do not set the max_memory in Postgres if duckdb.max_memory/duckdb.memory_limit is set to the empty string. ([#614])
• Handle PG columns with arrays with 0 dimensions correctly. We now assume such an array has a single dimension. ([#616])
• Fix valgrind issue in DatumToString. ([#639])
• Fix read of uninitialized memory when using DuckDB functions. ([#638])
• Fix escaping of MotherDuck schema names when syncing them. ([#650])
• Fix crash that could happen when EXPLAINing a prepared statement in certain cases. ([#660])
• Fix memory leak that could happen on query failure. ([#663])
• Add boundary checks when converting DuckDB date/timestamps to PG date/timestamps. DuckDB and Postgres don't support the exact same range of dates/timestamps, so now pg_duckdb only supports the intersection of these two ranges. ([#653])
• Fail nicely when syncing MotherDuck tables result in too long names being synced. ([#680]) TODO: FIX FOR TABLES CURRENTLY ONLY DONE FOR SCHEMAS
• Disallow installing pg_duckdb in databases with different encoding than UTF8. ([#703])
• Fix crashes or data corruption that could occur when using CREATE TABLE AS and materialized views if DuckDB execution and Postgres execution did not agree on the types that a query would return. ([#706])
• Fix various issues when using functions that returned duckdb.row (like read_csv & read_parquet) in a CTE. ([#718])
• Fix a crash when using a CREATE TABLE AS statement in a plpgqsl function ([#735])
• Throw error when trying to change DuckDB settings after the DuckDB connection has been initialized. ([#743])
• Fix crash for CREATE TABLE ... AS EXECUTE ([#757])
• Handle issues when DuckDB query would return different types between planning and execution phase. ([#759])
• Disallow DuckDB tables as a partition. This wasn't supported, and would fail in weird ways when attempted. Now a clear error is thrown. ([#778])
• Fix memory leak when reading LIST/JSON/JSONB columns from Postgres tables. ([#784])
• Fix dropping the Postgres side of a MotherDuck table, when the table does not exist anymore in MotherDuck. ([#784])
• Don't show hints about misuse of functions that return duckdb.row for queries that don't use those those functions. ([#811])
• Fix LIKE expressions involving a backslash (\) or LIKE ... ESCAPE expressions. ([#815])
• Fix errors for transactions that use SET TRANSACTION ISOLATION. ([#834])
• Fix compatibility issue with TimescaleDB extension. ([#846])
• Fix potential infinite loop during query cancelation ([#875])
• Fix do not allow relative path in DuckDB COPY statements. This is to provide the same protections as vanilla Postgres, so users don't accidentally overwrite database files. ([#827])
• Fix crashes involving postgres tables, by always materializing the entire DuckDB result set if the query involves Postgres tables. ([#877])

pg_duckdb is a Postgres extension that embeds DuckDB's columnar-vectorized analytics engine and features into Postgres. We recommend using pg_duckdb to build high performance analytics and data-intensive applications. See the README for install instructions and example usage. Below are the release notes for the 0.3.0 release. The only difference between 0.3.0 and 0.3.1 is a change to CI to fix pushing releases to Docker Hub.

Added

• Support using Postgres indexes and reading from partitioned tables. (#477)
• The AS (id bigint, name text) syntax is no longer supported when using read_parquet, iceberg_scan, etc. The new syntax is as follows: (#531)

  SELECT * FROM read_parquet('file.parquet');
  SELECT r['id'], r['name'] FROM read_parquet('file.parquet') r WHERE r['age'] > 21;

• Add a duckdb.query function which allows using DuckDB query syntax in Postgres. (#531)
• Support the approx_count_distinct DuckDB aggregate. (#499)
• Support the bytea (aka blob), uhugeint,jsonb, timestamp_ns, timestamp_ms, timestamp_s & interval types. (#511, #525, #513, #534, #573)
• Support DuckDB json functions and aggregates. (#546)
• Add support for the duckdb.allow_community_extensions setting.
• We have an official logo! 🎉 (#575)

Changed

• Update to DuckDB 1.2.0. (#548)
• Allow executing duckdb.raw_query, duckdb.cache_info, duckdb.cache_delete and duckdb.recycle_db as non-superusers. (#572)
• Only sync MotherDuck catalogs when there is DuckDB query activity. (#582)

Fixed

• Correctly parse parameter lists in COPY commands. This allows using PARTITION_BY as one of the COPY options. (#465)
• Correctly read cache metadata for files larger than 4GB. (#494)
• Fix bug in parameter handling for prepared statements and PL/pgSQL functions. (#491)
• Fix comparisons and operators on the timestamp with timezone field by enabling DuckDB its icu extension by default. (#512)
• Allow using read_parquet functions when not using superuser privileges. (#550)
• Fix some case insensitivity issues when reading from Postgres tables. (#563)
• Fix case where cancel requests (e.g. triggered by pressing Ctrl+C in psql) would be ignored (#548, #584, #587)
• Fixed CI so docker images are built and pushed to Docker Hub for tags. ([#589])

New Contributors

• @jhydra12 made their first contribution in #489
• @ritwizsinha made their first contribution in #512
• @szarnyasg made their first contribution in #519
• @elefeint made their first contribution in #528
• @dentiny made their first contribution in #543
• @destrex271 made their first contribution in #534

Full Changelog: v0.2.0...v0.3.1

pg_duckdb is a Postgres extension that embeds DuckDB's columnar-vectorized analytics engine and features into Postgres. We recommend using pg_duckdb to build high performance analytics and data-intensive applications. See the README for install instructions and example usage.

Added

• Support for reading Delta Lake storage using the duckdb.delta_scan(...) function. (#403)
• Support for reading JSON using the duckdb.read_json(...) function. (#405)
• Support for multi-statement transactions. (#433)
• Support reading from Azure Blob storage. (#478)
• Support many more array types, such as float , numeric and uuid arrays. (#282)
• Support for PostgreSQL 14. (#397)
• Manage cached files using the duckdb.cache_info() and duckdb.cache_delete() functions. (#434)
• Add scope column to duckdb.secrets table. (#461)
• Allow configuring the default MotherDuck database using the duckdb.motherduck_default_database setting. (#470)
• Automatically install and load known DuckDB extensions when queries use them. So, duckdb.install_extension() is usually not necessary anymore. (#484)

Changed

• Improve performance of heap reading. (#366)
• Bump DuckDB version to 1.1.3. (#400)

Fixed

• Throw a clear error when reading partitioned tables (reading from partitioned tables is not supported yet). (#412)
• Fixed crash when using CREATE SCHEMA AUTHORIZATION. (#423)
• Fix queries inserting into DuckDB tables with DEFAULT values. (#448)
• Fixed assertion failure involving recursive CTEs. (#436)
• Only allow setting duckdb.motherduck_postgres_database in postgresql.conf. (#476)
• Much better separation between C and C++ code, to avoid memory leaks and crashes (many PRs).

New Contributors

• @Reminiscent made their first contribution in #282
• @dpxcc made their first contribution in #443
• @naoyak made their first contribution in #470

Full Changelog: v0.1.0...v0.2.0

Initial release 🎉