Repository navigation
Releases
pgvfs 0.3.2
Fixes for the DuckDB 2.0 and nightly builds: 2.0 caches pgdb:// reads again, the container build links pgdb_filesystem.cpp, and the nightly has its dbschema.sql.
INSTALL pgvfs FROM 'https://pgvfs.adonm.dev'; -- DuckDB 1.5.6, or a 2.0 dev build
LOAD pgvfs;What's in 0.3.2
Storage layout: v2 (unchanged).
- DuckDB 2.0 caches
pgdb://reads again. 2.0 caches only paths that look
remote, and loading pgvfs now turns oncache_local_fileswhere it exists, so
the external file cache servespgdb://reads (1.5.6 is unaffected: it has no
such rule and no such setting). - The nightly build works again: the container had not copied
dbschema.sql(needed since 0.3.0), andextension/build.shhad not been
givenpgdb_filesystem.cpp. A failed nightly build now prints the compiler's
error instead of only docker's. just ext-nightlypasses--hostname github.comtogh, so it works for a
developer whoseghdefaults to another host.- The contract's PostgreSQL allows 500 connections (the pgdb end-to-end test
uses more than the default 100 under 2.0) and the Python end-to-end test runs
withPGVFS_POOL_MIN=1 PGVFS_POOL_MAX=8, as the Rust contract does.
Docs: https://pgvfs.adonm.dev · Changelog: https://github.com/adonm/pgvfs/blob/v0.3.2/CHANGELOG.md · All builds: https://pgvfs.adonm.dev/install.html#builds
pgvfs 0.3.1
pgdb:// reads ahead: a cold scan stops paying a round trip per block (2.60 s to 0.70 s for a 1.2 GB scan), with no change to point lookups.
INSTALL pgvfs FROM 'https://pgvfs.adonm.dev'; -- DuckDB 1.5.6, or a 2.0 dev build
LOAD pgvfs;What's in 0.3.1
Storage layout: v2 (unchanged). No FFI or table changes.
pgdb://reads ahead. A read that continues the previous one also
fetches the blocks after it, so scans stop costing a round trip per block
(2.6 s to 0.70 s for a cold 1.2 GB scan with 16 KiB blocks, 438 ms to 163 ms
with 8 threads) and range scans nearly halve. A read after a gap fetches
exactly its own bytes, so point lookups are unchanged. Knobs:
PGVFS_DB_READAHEAD_KB(1 MiB) andPGVFS_DB_READAHEAD_SLOTS(8). New
counters:db_readahead_hits,db_readahead_bytes.- Block size is documented as a knob (
BLOCK_SIZEat creation):
Databases. - Comments trimmed across the Rust and C++ sources; the house style is in
CONTRIBUTING.md.
Docs: https://pgvfs.adonm.dev · Changelog: https://github.com/adonm/pgvfs/blob/v0.3.1/CHANGELOG.md · All builds: https://pgvfs.adonm.dev/install.html#builds
pgvfs for DuckDB v2.0.0-alpha43763
Built from e1d6eb4 on 2026-10-14 for duckdb==2.0.0.dev2610011535 (linux_amd64).
INSTALL pgvfs FROM 'https://pgvfs.adonm.dev'; -- picks this build for DuckDB v2.0.0-alpha43763pgvfs for DuckDB v1.5.6
Built from 86c1a99 on 2026-11-16 for duckdb==1.5.6 (linux_amd64).
INSTALL pgvfs FROM 'https://pgvfs.adonm.dev'; -- picks this build for DuckDB v1.5.6pgvfs 0.3.0
Native DuckDB databases in PostgreSQL: ATTACH 'pgdb://<volume>/<name>' is a real DuckDB database (indexes, keys, constraints, WAL) with one writer and any number of readers that follow new commits by themselves.
INSTALL pgvfs FROM 'https://pgvfs.adonm.dev'; -- DuckDB 1.5.6, or a 2.0 dev build
LOAD pgvfs;What's in 0.3.0
Storage layout: v2 (unchanged). pgdb:// adds five tables
(dbschema.sql), created by the first database writer; the pgvfs:// tables
do not change.
pgdb://: native DuckDB databases in PostgreSQL (experimental).ATTACH 'pgdb://<volume>/<name>'is a real DuckDB database (ART indexes, primary and
foreign keys, constraints, sequences, WAL) stored as versioned 8 KB chunks.
One writer, refused at attach if another holds it and fenced on every write;
any number of readers, on standbys too, each reading one published version
and re-attached at the newest everypgdb_refresh_intervalseconds (running
transactions keep theirs). Readers cache through DuckDB's external file cache
under keys a new version leaves valid. Experimental: its tables may still
change, with a migration. See
Databases for the design, limits
and benchmarks: against a local file, warm readers run at 93% of the
throughput, loads at 1.24x the time, commits at about 2 ms; cold scattered
lookups are the slow case.- Concurrent searches of one tantivy split read in parallel, through up to
four handles instead of one under a lock. - Secrets are found for database-level I/O (no client context), through
the file opener. pgvfs_stats()addsdb_reads,db_read_bytes,db_pieces,
db_cache_bytesanddb_publishes.- Tests and benchmarks:
just bench-db(pgdb://against a local DuckDB
file),just sqllogic(DuckDB's own SQL tests onpgdb://), and a
pgdb://storage contract and end-to-end test injust contract.
Upgrading from beta.6: nothing to do. Readers of pgdb:// need SELECT on the
new tables, writers INSERT, UPDATE and DELETE (see
Databases).
Docs: https://pgvfs.adonm.dev · Changelog: https://github.com/adonm/pgvfs/blob/v0.3.0/CHANGELOG.md · All builds: https://pgvfs.adonm.dev/install.html#builds
pgvfs 0.2.0-beta.5
Storage layout v2 (unchanged). Full changelog: CHANGELOG.md.
Full-text search (tantivy, same extension)
- Exclusion as a per-segment alive bitset: with 60% of 4M documents excluded, a count takes 9 ms (was 61), a top 10 takes 6 ms (was 64).
- A list of splits is searched in parallel;
offset,collapse,sortby a fast field,highlight(a fourthhighlightcolumn),ignore_unmapped; countlimitanddistinct. - Query DSL: paths inside JSON fields,
prefix/wildcard/regexp/fuzzyon them,case_insensitive,more_like_this. - Every function registers a description and an example.
Fixes
- Prepared index plans and a failed build open under a parallel
GROUP BYno longer crash. - DuckDB 2.0: a hash join on a key read from
tantivy_searchhits found nothing.
Build: C headers are generated from the Rust FFI and checked in CI; cargo-deny checks licences and sources; property tests over the search.
Built and tested for DuckDB 1.5.6 and 2.0 on Linux (glibc, musl), macOS and Windows: distribution run.
pgvfs for DuckDB v2.0.0-alpha43385
Built from 271c57b on 2026-09-29 for duckdb==2.0.0.dev2609250715 (linux_amd64).
INSTALL pgvfs FROM 'https://pgvfs.adonm.dev'; -- picks this build for DuckDB v2.0.0-alpha43385Weekly benchmark history
Concurrent-readers benchmark (bench/readers.py), one line per reader count per run.