Results of 1 - 10 of about 11 for production (0.002 sec.)
- Securing Quack with a Reverse Proxy 13994
- By default, the Quack server binds to localhost and speaks plain HTTP. See Security for the rationale behind these configurations. For any deployment beyond local-only, the recommended pattern is the same as for any other HTTP-based databas
...ness: A local TLS test setup with Caddy, so you can exercise the full HTTPS path on your machine. nginx + Let's Encrypt in production. Caddy + Let's Encrypt in production. The two production setups are interchangeable. Pick whichever fits your operational... - https://man.mtool.work/duckdb/2.0/quack/setup/reverse_proxy.html
- Concurrency 9779
- Handling Concurrency Single Process In in-process mode, DuckDB has two configurable options for concurrency: Read-write mode: one process can both read and write to the database. Read-only mode: multiple processes can read from the database
...PostgreSQL catalog, DuckDB instances can achieve concurrent read-writes on the same database. DuckLake 1.1 , intended for production use, was released alongside DuckDB 2.0. Optimistic Concurrency Control DuckDB uses optimistic concurrency control , an app... - https://man.mtool.work/duckdb/2.0/connect/concurrency.html
- Security 9779
- This page covers Quack's security posture end to end: what the server exposes, what stays local, the role of a TLS-terminating reverse proxy, and the authentication / authorization callbacks the server runs on every connection and every que
...fronted server "just works" from the client side too. See Securing Quack with a Reverse Proxy for nginx and Caddy recipes (production and local-test). Authentication and Authorization For every database call, there are two distinct decisions to be made: Au...-only filter: a query like WITH x AS (SELECT 1) INSERT INTO t SELECT * FROM x starts with WITH yet still mutates data. For production read-only enforcement, attach the database in read-only mode or use an authorization function that inspects the parsed sta... - https://man.mtool.work/duckdb/2.0/quack/security.html
- DuckDB Wasm Client 8730
- Installation To use the DuckDB Wasm client, visit the duckdb-wasm GitHub repository . The latest stable version of the DuckDB WebAssembly client is 2.0.0. DuckDB-Wasm is a version of DuckDB that has been compiled to WebAssembly , the portab
...the next tag with npm install @duckdb/duckdb-wasm@next ; it tracks the main branch and is intended for testing rather than production. Alternatively, load a prebuilt bundle directly from a CDN such as jsDelivr without installing anything; see Instantiate f... - https://man.mtool.work/duckdb/2.0/clients/wasm/overview.html
- Write User Defined Functions 8375
- Overview The Rust client can register user-defined functions written in Rust: scalar functions with the vscalar feature and table functions with the vtab feature. Both operate on DuckDB's columnar data chunks, so a single call processes a b
...calls; use () when none is needed. The example reads its input as a typed slice for brevity and assumes non-null input; a production function should also check each value's validity. This feature requires features = ["vscalar"] . Table Functions A table f... - https://man.mtool.work/duckdb/2.0/clients/rust/functions.html
- Migrating to DuckDB 2.0 8019
- DuckDB 2.0.0 is packed with new features and performance improvements, including query optimization and asynchronous I/O. It also ships a small set of breaking changes, most notably a new default storage format, which DuckDB versions before
...g up a shadow system that tracks your existing workload. This lets you test DuckDB 2.0.0 in an environment outside of your production system before switching over. For simple deployments, migrating is straightforward. Complex deployments, especially those... - https://man.mtool.work/duckdb/2.0/operations_manual/migration.html
- Quack Remote Protocol 8019
- The Quack extension turns a DuckDB instance into a server that other DuckDB instances (clients) can connect to over HTTP. This page covers the protocol at a glance and walks through basic usage on both sides of the wire. For the full list o
...HTTPS by default, using a self-signed certificate unless you pass ssl_cert_file and ssl_key_file (see the Reference ). For production deployments, we recommend binding the server to localhost and fronting it with a TLS-terminating reverse proxy. See Securi... - https://man.mtool.work/duckdb/2.0/quack/overview.html
- Reference 8019
- This page lists the functions, settings, and log types exposed by the quack extension . For a tour of the protocol, start with the Overview . Function Reference Server Management Function Description quack_serve(⟨listen_uri⟩, ...) Start a s
...nsion also registers several quack_debug_* settings, which are intended for testing the protocol and should not be used in production. Node Identity These settings back the whoami() macro. quack_identify(...) is sugar that updates them. Setting Type Defaul... - https://man.mtool.work/duckdb/2.0/quack/reference.html
- Pragmas 7663
- The PRAGMA statement is a SQL extension adopted by DuckDB from SQLite. PRAGMA statements can be issued in a similar manner to regular SQL statements. PRAGMA commands may alter the internal state of the database engine, and can influence the
...= ''; Warning The disabled_optimizers option should only be used for debugging performance issues and should be avoided in production. Logging Set a path for query logging: SET log_query_path = '/tmp/duckdb_log/'; Disable query logging: SET log_query_path... - https://man.mtool.work/duckdb/2.0/configuration/pragmas.html
- PostgreSQL Extension 7663
- The postgres extension allows DuckDB to directly read and write data from a running PostgreSQL database instance. The data can be queried directly from the underlying PostgreSQL database. Data can be loaded from PostgreSQL tables into DuckD
...ent Variables PostgreSQL connection information can also be specified with environment variables . This can be useful in a production environment where the connection information is managed externally and passed in to the environment. export PGPASSWORD="se... - https://man.mtool.work/duckdb/2.0/core_extensions/postgres/overview.html
DuckDB 2.0 Documentation / man.mtool.work