AI vendors and your data

Vendors146Answers427

146 vendors · 427 answers

Frequently Asked Questions changed DuckDB, Oct 26, 2026

DuckDB · Oct 26, 2026 · 13 added, 10 removed · seen by the weekly check

The pageAll DuckDB terms
  1. Added: DuckLabs is a company based in Amsterdam that provides commercial support services for DuckDB. DuckLabs employs the core contributors of the DuckDB project. DuckLabs joined AWS in September 2026 .
  2. Removed: DuckLabs is based in Amsterdam that provides commercial support services for DuckDB. DuckLabs employs the core contributors of the DuckDB project. DuckLabs will join AWS from September 2026 .
  3. Added: It is a common misconception that DuckDB is an in-memory database. While DuckDB can work in-memory, it is not an in-memory database . DuckDB can make use of available memory for caching, but it also fully supports disk-based persistence and offloading larger-than-memory operations to disk.
  4. Removed: It is a common misconception that DuckDB is an in-memory database. While DuckDB can work in-memory, it is not an in-memory database . DuckDB can make use of available memory for caching, it also fully supports disk-based persistence and offloading larger-than-memory operations to disk.
  5. Added: Since version 0.10.0 (released in February 2024), DuckDB is backwards-compatible when reading database files, i.e., newer versions of DuckDB are always able to read database files created with an older version of DuckDB. DuckDB also provides partial forwards-compatibility on a best-effort basis. Note that DuckDB versions before 2.0 cannot read database files created by DuckDB 2.0 unless they were written with an explicit storage version . See the storage page for more details. Compatibility is also guaranteed between different DuckDB clients (e.g., Python and R): a database file created with one client can be read with other clients.
  6. Removed: Since version 0.10.0 (released in February 2024), DuckDB is backwards-compatible when reading database files, i.e., newer versions of DuckDB are always able to read database files created with an older version of DuckDB. DuckDB also provides partial forwards-compatibility on a best-effort basis. See the storage page for more details. Compatibility is also guaranteed between different DuckDB clients (e.g., Python and R): a database file created with one client can be read with other clients.
  7. Added: See the documentation on handling concurrency and the section on "Multiple Processes" .
  8. Removed: See the documentation on handling concurrency and the section on "Writing to DuckDB from Multiple Processes" .
  9. Added: The DuckLake format through the ducklake extension with PostgreSQL as the catalog database. This is a production-ready solution .
  10. Added: The Quack remote protocol , which turns DuckDB into a client-server database. Quack was introduced in DuckDB v1.5.3, and DuckDB v2.0 ships a polished version of the protocol.
  11. Removed: The DuckLake format through the ducklake extension with PostgreSQL as the catatalog database. This is a production-ready solution .
  12. Removed: The Quack remote protocol , which turns DuckDB into a client-server database. Quack is in beta stage as of DuckDB v1.5.2, and is expected to become mature by DuckDB v2.0 in fall 2026 .
  13. Added: For data science users, who often run queries in an interactive fashion, DuckDB offers several mechanisms for quickly exploring data sets. For example, CSV files can be loaded by auto-inferring their schema using CREATE TABLE tbl AS FROM 'input.csv' . Moreover, there are numerous SQL shorthands known as "friendly SQL" for more concise expressions, e.g., the GROUP BY ALL clause .
  14. Removed: For data science users, who often run queries in an interactive fashion, DuckDB offers several mechanisms for quickly exploring data sets. For example, CSV files can be loaded by auto-inferring their schema using CREATE TABLE tbl AS FROM 'input.csv' . Moreover, there numerous SQL shorthands known as "friendly SQL" for more concise expressions, e.g., the GROUP BY ALL clause .
  15. Added: If you have a feature idea, please raise an issue in the "Ideas" section in DuckDB's GitHub Discussions . The DuckDB team monitors these ideas and, over time, implements the frequently requested features. For example, reading Avro files was once the most requested feature in the issue tracker; it is now supported by the avro extension .
  16. Removed: If you have a feature idea, please raise an issue in the "Ideas" section in DuckDB's GitHub Discussions . The DuckDB team monitors these ideas and, over time, implements the frequently requested features. For example, we recently published the Avro Community Extension to support reading Avro files, which was the most requested feature in the issue tracker.
  17. Added: DuckDB v2.0 (LTS, supported until October 2027)
  18. Added: DuckDB v1.5 (extended support until March 2027)
  19. Added: DuckDB v1.4 (LTS, supported until November 2026)
  20. Added: For end-of-life dates, see the release calendar .
  21. Removed: latest LTS (long-term support) version, presently 1.4
  22. Added: New feature releases (e.g., v1.2.0) are released every 3-7 months. Bugfix releases (e.g., v1.1.3) are released every 2-4 weeks after a feature release. You can find the recent releases in the Release Calendar .
  23. Removed: New feature releases (e.g., v1.2.0) are released every 3-5 months. Bugfix releases (e.g., v1.1.3) are released every 2-4 weeks after a feature release. You can find the recent releases in the Release Calendar .
About this change
Page
duckdb.org/faq
Kind
Documentation
Text hash
88aca4046b96 to d5d4bc5fe53e
Dated by
the weekly check that first read the new text