biscuit

Overview

rename from pg_biscuit to biscuit to keep up with PGDG RPM name

Version

Build

You can build the RPM / DEB packages for pg_biscuit using pig build:

pig build pkg pg_biscuit         # build RPM / DEB packages

Install

You can install pg_biscuit directly. First, make sure the PGDG and PIGSTY repositories are added and enabled:

pig repo add pgsql -u          # Add repo and update cache

Install the extension using pig or apt/yum/dnf:

• Install
• pig
• dnf
• apt

pig install pg_biscuit;          # Install for current active PG version

pig ext install -y pg_biscuit -v 18  # PG 18
pig ext install -y pg_biscuit -v 17  # PG 17
pig ext install -y pg_biscuit -v 16  # PG 16

dnf install -y biscuit_18       # PG 18
dnf install -y biscuit_17       # PG 17
dnf install -y biscuit_16       # PG 16

apt install -y postgresql-18-biscuit   # PG 18
apt install -y postgresql-17-biscuit   # PG 17
apt install -y postgresql-16-biscuit   # PG 16

Create Extension:

CREATE EXTENSION biscuit CASCADE;  -- requires: plpgsql

Usage

Sources:

• PGXN biscuit 2.4.1
• Biscuit README
• Biscuit CHANGELOG
• Biscuit documentation
• Local package metadata

biscuit is a PostgreSQL index access method for accelerating LIKE, NOT LIKE, ILIKE, and NOT ILIKE pattern matching on text. It uses bitmap-style position indexes to avoid the heap recheck overhead common in trigram searches and supports multi-column indexes for wildcard-heavy workloads.

PGXN package 2.4.1 ships the SQL/control version 2.4.0; the extension’s visible default_version is therefore still 2.4.0. The local Pigsty extension name is biscuit, while older package metadata may mention pg_biscuit.

Quick Start

CREATE EXTENSION IF NOT EXISTS biscuit;

CREATE TABLE users (
  id bigserial PRIMARY KEY,
  name text,
  email text,
  bio text
);

CREATE INDEX users_name_biscuit
ON users USING biscuit (name);

SELECT *
FROM users
WHERE name LIKE '%john%';

biscuit supports ordinary wildcard patterns with % and _:

SELECT * FROM users WHERE name LIKE 'john%';
SELECT * FROM users WHERE name LIKE '%smith';
SELECT * FROM users WHERE name LIKE '%oh_';
SELECT * FROM users WHERE name ILIKE '%john%';
SELECT * FROM users WHERE name NOT LIKE '%test%';

Multi-Column Indexes

CREATE INDEX users_search_biscuit
ON users USING biscuit (name, email, bio);

SELECT *
FROM users
WHERE name ILIKE '%john%'
  AND email LIKE '%example.com'
  AND bio NOT LIKE '%inactive%';

Biscuit can combine bitmap matches from multiple indexed columns and may reorder predicates by estimated selectivity.

Expression Indexes

Version 2.4.0 adds expression-index support:

CREATE INDEX users_lower_name_biscuit
ON users USING biscuit (lower(name));

SELECT *
FROM users
WHERE lower(name) LIKE '%john%';

For char(n) / bpchar columns, upstream recommends expression indexes that cast to text, because native bpchar operator classes are not yet available:

CREATE INDEX legacy_code_biscuit
ON legacy_table USING biscuit ((code::text));

Introspection

SELECT *
FROM biscuit_operators;

SELECT *
FROM biscuit_version_history;

The biscuit_operators view lists the operators registered for the Biscuit access method. In 2.4.0, the view was fixed to remain correct if additional operator classes or families are added.

Operational Notes

Biscuit’s design is optimized for:

• prefix, suffix, substring, and mixed wildcard LIKE / ILIKE patterns
• multi-column predicates where bitmap intersections can reduce candidate sets
• exact pattern matching without trigram false-positive rechecks
• workloads where text-pattern search dominates query latency

It is not a general full-text search engine and does not replace ranking, stemming, tokenization, or phrase search. Use PostgreSQL full text search, trigram indexes, or dedicated search extensions when those semantics are required.

Caveats

• Upstream requires PostgreSQL 16 or newer and standard build tools. Pigsty local metadata currently packages Biscuit for PostgreSQL 16-18.
• PGXN package version 2.4.1 carries SQL/control default_version = '2.4.0'; this is expected for the current source package.
• Biscuit only targets LIKE / ILIKE-style wildcard matching. Regular expressions are not the supported search surface.
• Non-text columns should be indexed through explicit text expressions when needed.
• Benchmark against pg_trgm and your actual data distribution before replacing existing production indexes.