Category: FTS

• 1: pg_search
• 2: pgroonga
• 3: pgroonga_database
• 4: pg_bigm
• 5: zhparser
• 6: pg_bestmatch
• 7: vchord_bm25
• 8: hunspell_cs_cz
• 9: hunspell_de_de
• 10: hunspell_en_us
• 11: hunspell_fr
• 12: hunspell_ne_np
• 13: hunspell_nl_nl
• 14: hunspell_nn_no
• 15: hunspell_pt_pt
• 16: hunspell_ru_ru
• 17: hunspell_ru_ru_aot
• 18: fuzzystrmatch
• 19: pg_trgm

1 - pg_search

Overview

PIGSTY 3rd Party Extension: pg_search : pg_search: Full text search for PostgreSQL using BM25

Information

• Extension ID: 2100
• Extension Name: pg_search
• Package Name: pg_search
• Category: FTS
• License: AGPLv3
• Website: https://github.com/paradedb/paradedb/tree/dev/pg_search
• Language: Rust
• Extra Tags: pgrx
• Comment: N/A

Metadata

• Latest Version: 0.15.1
• Postgres Support: 17,16,15,14
• Need Load: Shared library do not need explicit loading
• Need DDL: Need CREATE EXTENSION DDL
• Relocatable: Can be installed into other schemas
• Trusted: Trusted, Can be created by user with CREATE Privilege
• Schemas: paradedb
• Requires: N/A

RPM / DEB

• RPM Repo: PIGSTY
• RPM Name: pg_search_$v
• RPM Ver : 0.15.1
• RPM Deps: N/A
• DEB Repo: PIGSTY
• DEB Name: postgresql-$v-pg-search
• DEB Ver : 0.15.1
• DEB Deps: N/A

Packages

Installation

Install pg_search via the pig CLI tool:

pig ext install pg_search

Install pg_search via Pigsty playbook:

./pgsql.yml -t pg_extension -e '{"pg_extensions": ["pg_search"]}' # -l <cls>

Install pg_search RPM from YUM repo directly:

dnf install pg_search_17;
dnf install pg_search_16;
dnf install pg_search_15;
dnf install pg_search_14;

Install pg_search DEB from APT repo directly:

apt install postgresql-17-pg-search;
apt install postgresql-16-pg-search;
apt install postgresql-15-pg-search;
apt install postgresql-14-pg-search;

Enable pg_search extension on PostgreSQL cluster：

CREATE EXTENSION pg_search;

Usage

https://docs.paradedb.com/documentation/getting-started/quickstart

CREATE EXTENSION pg_search;

ALTER SYSTEM SET paradedb.pg_search_telemetry TO 'off';

CALL paradedb.create_bm25_test_table(
  schema_name => 'public',
  table_name => 'mock_items'
);
    
SELECT description, rating, category FROM mock_items LIMIT 3;

CALL paradedb.create_bm25(
        index_name => 'search_idx',
        schema_name => 'public',
        table_name => 'mock_items',
        key_field => 'id',
        text_fields => paradedb.field('description', tokenizer => paradedb.tokenizer('en_stem')) ||
                       paradedb.field('category'),
        numeric_fields => paradedb.field('rating')
     );

SELECT description, rating, category
FROM search_idx.search('(description:keyboard OR category:electronics) AND rating:>2',limit_rows => 5);

CALL paradedb.create_bm25(
        index_name => 'ngrams_idx',
        schema_name => 'public',
        table_name => 'mock_items',
        key_field => 'id',
        text_fields => paradedb.field('description', tokenizer => paradedb.tokenizer('ngram', min_gram => 4, max_gram => 4, prefix_only => false)) ||
                       paradedb.field('category')
     );

SELECT description, rating, category
FROM ngrams_idx.search('description:blue');

2 - pgroonga

Overview

PIGSTY 3rd Party Extension: pgroonga : Use Groonga as index, fast full text search platform for all languages!

Information

• Extension ID: 2110
• Extension Name: pgroonga
• Package Name: pgroonga
• Category: FTS
• License: PostgreSQL
• Website: https://github.com/pgroonga/pgroonga
• Language: C
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 4.0.0
• Postgres Support: 17,16,15,14,13
• Need Load: Shared library do not need explicit loading
• Need DDL: Need CREATE EXTENSION DDL
• Relocatable: Can not install to arbitrary schema
• Trusted: Trusted, Can be created by user with CREATE Privilege
• Schemas: N/A
• Requires: N/A

RPM / DEB

• RPM Repo: PIGSTY
• RPM Name: pgroonga_$v*
• RPM Ver : 4.0.0
• RPM Deps: groonga-libs
• DEB Repo: PIGSTY
• DEB Name: postgresql-$v-pgroonga
• DEB Ver : 4.0.0
• DEB Deps: libgroonga0

Packages

Installation

Install pgroonga via the pig CLI tool:

pig ext install pgroonga

Install pgroonga via Pigsty playbook:

./pgsql.yml -t pg_extension -e '{"pg_extensions": ["pgroonga"]}' # -l <cls>

Install pgroonga RPM from YUM repo directly:

dnf install pgroonga_17*;
dnf install pgroonga_16*;
dnf install pgroonga_15*;
dnf install pgroonga_14*;
dnf install pgroonga_13*;

Install pgroonga DEB from APT repo directly:

apt install postgresql-17-pgroonga;
apt install postgresql-16-pgroonga;
apt install postgresql-15-pgroonga;
apt install postgresql-14-pgroonga;
apt install postgresql-13-pgroonga;

Enable pgroonga extension on PostgreSQL cluster：

CREATE EXTENSION pgroonga;

Usage

• https://pgroonga.github.io/
• News: It lists release information.
• Overview: It describes about PGroonga.
• Install: It describes how to install PGroonga.
• Upgrade: It describes how to upgrade PGroonga.
• Uninstall: It describes how to uninstall PGroonga.
• Tutorial: It describes how to use PGroonga step by step.
• FAQ: Frequently asked questions.
• How to: It describes about useful information for specific situations.
• Reference: It describes details for each features such as options, functions and operators.
• Troubleshooting: It describes how to fix troubles.
• Community: It introduces about PGroonga community.
• Users: It lists PGroonga users.
• Development: It describes how to develop PGroonga.

Here’s a quick tutorial about how to use PGroonga:

CREATE EXTENSION IF NOT EXISTS pgroonga;

CREATE TABLE memos
(
    id      integer,
    content text
);

CREATE INDEX pgroonga_content_index ON memos USING pgroonga (content);

INSERT INTO memos VALUES (1, 'PostgreSQL is a relational database management system.');
INSERT INTO memos VALUES (2, 'Groonga is a fast full text search engine that supports all languages.');
INSERT INTO memos VALUES (3, 'PGroonga is a PostgreSQL extension that uses Groonga as index.');
INSERT INTO memos VALUES (4, 'There is groonga command.');

SET enable_seqscan = off;

-- now let's query pgroonga

SELECT * FROM memos WHERE content &@ 'engine';
--  id |                                content                                 
-- ----+------------------------------------------------------------------------
--   2 | Groonga is a fast full text search engine that supports all languages.
-- (1 row)

SELECT * FROM memos WHERE content &@~ 'PGroonga OR PostgreSQL';
--  id |                            content                             
-- ----+----------------------------------------------------------------
--   3 | PGroonga is a PostgreSQL extension that uses Groonga as index.
--   1 | PostgreSQL is a relational database management system.
-- (2 rows)

SELECT * FROM memos WHERE content LIKE '%engine%';
--  id |                                content                                 
-- ----+------------------------------------------------------------------------
--   2 | Groonga is a fast full text search engine that supports all languages.
-- (1 row)

3 - pgroonga_database

Overview

PIGSTY 3rd Party Extension: pgroonga : PGroonga database management module

Information

• Extension ID: 2111
• Extension Name: pgroonga_database
• Package Name: pgroonga
• Category: FTS
• License: PostgreSQL
• Website: https://github.com/pgroonga/pgroonga
• Language: C
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 4.0.0
• Postgres Support: 17,16,15,14,13
• Need Load: Shared library do not need explicit loading
• Need DDL: Need CREATE EXTENSION DDL
• Relocatable: Can not install to arbitrary schema
• Trusted: Trusted, Can be created by user with CREATE Privilege
• Schemas: N/A
• Requires: N/A

RPM / DEB

• RPM Repo: PIGSTY
• RPM Name: pgroonga_$v*
• RPM Ver : 4.0.0
• RPM Deps: groonga-libs
• DEB Repo: PIGSTY
• DEB Name: postgresql-$v-pgroonga
• DEB Ver : 4.0.0
• DEB Deps: libgroonga0

Packages

Installation

Install pgroonga_database via the pig CLI tool:

pig ext install pgroonga; # Extension Namepig ext install pgroonga_database; # normalized package name

Install pgroonga via Pigsty playbook:

./pgsql.yml -t pg_extension -e '{"pg_extensions": ["pgroonga"]}' # -l <cls>

Install pgroonga RPM from YUM repo directly:

dnf install pgroonga_17*;
dnf install pgroonga_16*;
dnf install pgroonga_15*;
dnf install pgroonga_14*;
dnf install pgroonga_13*;

Install pgroonga DEB from APT repo directly:

apt install postgresql-17-pgroonga;
apt install postgresql-16-pgroonga;
apt install postgresql-15-pgroonga;
apt install postgresql-14-pgroonga;
apt install postgresql-13-pgroonga;

Enable pgroonga_database extension on PostgreSQL cluster：

CREATE EXTENSION pgroonga_database;

4 - pg_bigm

Overview

MIXED 3rd Party Extension: pg_bigm : create 2-gram (bigram) index for faster full text search.

Information

• Extension ID: 2120
• Extension Name: pg_bigm
• Package Name: pg_bigm
• Category: FTS
• License: PostgreSQL
• Website: https://github.com/pgbigm/pg_bigm
• Language: C
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 1.2
• Postgres Support: 17,16,15,14,13
• Need Load: Shared library do not need explicit loading
• Need DDL: Need CREATE EXTENSION DDL
• Relocatable: Can not install to arbitrary schema
• Trusted: Untrusted, Require Superuser to Create
• Schemas: N/A
• Requires: N/A

RPM / DEB

• RPM Repo: PGDG
• RPM Name: pg_bigm_$v*
• RPM Ver : 1.2
• RPM Deps: N/A
• DEB Repo: PIGSTY
• DEB Name: postgresql-$v-pg-bigm
• DEB Ver : 1.2
• DEB Deps: N/A

Packages

Installation

Install pg_bigm via the pig CLI tool:

pig ext install pg_bigm

Install pg_bigm via Pigsty playbook:

./pgsql.yml -t pg_extension -e '{"pg_extensions": ["pg_bigm"]}' # -l <cls>

Install pg_bigm RPM from YUM repo directly:

dnf install pg_bigm_17*;
dnf install pg_bigm_16*;
dnf install pg_bigm_15*;
dnf install pg_bigm_14*;
dnf install pg_bigm_13*;

Install pg_bigm DEB from APT repo directly:

apt install postgresql-17-pg-bigm;
apt install postgresql-16-pg-bigm;
apt install postgresql-15-pg-bigm;
apt install postgresql-14-pg-bigm;
apt install postgresql-13-pg-bigm;

Enable pg_bigm extension on PostgreSQL cluster：

CREATE EXTENSION pg_bigm;

5 - zhparser

Overview

PIGSTY 3rd Party Extension: zhparser : a parser for full-text search of Chinese

Information

• Extension ID: 2130
• Extension Name: zhparser
• Package Name: zhparser
• Category: FTS
• License: PostgreSQL
• Website: https://github.com/amutu/zhparser
• Language: C
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 2.3
• Postgres Support: 17,16,15,14,13
• Need Load: Shared library do not need explicit loading
• Need DDL: Need CREATE EXTENSION DDL
• Relocatable: Can not install to arbitrary schema
• Trusted: Untrusted, Require Superuser to Create
• Schemas: N/A
• Requires: N/A

RPM / DEB

• RPM Repo: PIGSTY
• RPM Name: zhparser_$v*
• RPM Ver : 2.3
• RPM Deps: N/A
• DEB Repo: PIGSTY
• DEB Name: postgresql-$v-zhparser
• DEB Ver : 2.3
• DEB Deps: N/A

Packages

Installation

Install zhparser via the pig CLI tool:

pig ext install zhparser

Install zhparser via Pigsty playbook:

./pgsql.yml -t pg_extension -e '{"pg_extensions": ["zhparser"]}' # -l <cls>

Install zhparser RPM from YUM repo directly:

dnf install zhparser_17*;
dnf install zhparser_16*;
dnf install zhparser_15*;
dnf install zhparser_14*;
dnf install zhparser_13*;

Install zhparser DEB from APT repo directly:

apt install postgresql-17-zhparser;
apt install postgresql-16-zhparser;
apt install postgresql-15-zhparser;
apt install postgresql-14-zhparser;
apt install postgresql-13-zhparser;

Enable zhparser extension on PostgreSQL cluster：

CREATE EXTENSION zhparser;

6 - pg_bestmatch

Overview

PIGSTY 3rd Party Extension: pg_bestmatch : Generate BM25 sparse vector inside PostgreSQL

Information

• Extension ID: 2140
• Extension Name: pg_bestmatch
• Package Name: pg_bestmatch
• Category: FTS
• License: Apache-2.0
• Website: https://github.com/tensorchord/pg_bestmatch.rs
• Language: Rust
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 0.0.1
• Postgres Support: 17,16,15,14,13
• Need Load: Explicit Loading Required
• Need DDL: Need CREATE EXTENSION DDL
• Relocatable: Can be installed into other schemas
• Trusted: Untrusted, Require Superuser to Create
• Schemas: bm_catalog
• Requires: N/A

RPM / DEB

• RPM Repo: PIGSTY
• RPM Name: pg_bestmatch_$v
• RPM Ver : 0.0.1
• RPM Deps: N/A
• DEB Repo: PIGSTY
• DEB Name: postgresql-$v-pg-bestmatch
• DEB Ver : 0.0.1
• DEB Deps: N/A

Packages

Installation

Install pg_bestmatch via the pig CLI tool:

pig ext install pg_bestmatch

Install pg_bestmatch via Pigsty playbook:

./pgsql.yml -t pg_extension -e '{"pg_extensions": ["pg_bestmatch"]}' # -l <cls>

Install pg_bestmatch RPM from YUM repo directly:

dnf install pg_bestmatch_17;
dnf install pg_bestmatch_16;
dnf install pg_bestmatch_15;
dnf install pg_bestmatch_14;
dnf install pg_bestmatch_13;

Install pg_bestmatch DEB from APT repo directly:

apt install postgresql-17-pg-bestmatch;
apt install postgresql-16-pg-bestmatch;
apt install postgresql-15-pg-bestmatch;
apt install postgresql-14-pg-bestmatch;
apt install postgresql-13-pg-bestmatch;

Extension pg_bestmatch has to be added to shared_preload_libraries

shared_preload_libraries = 'pg_bestmatch'; # add to pg cluster config

Enable pg_bestmatch extension on PostgreSQL cluster：

CREATE EXTENSION pg_bestmatch;

Usage

• repo: https://github.com/tensorchord/pg_bestmatch.rs
• benchmark: https://hazyresearch.stanford.edu/blog/2024-05-20-m2-bert-retrieval

How does it work?

• Create an BM25 statistics based on your document set by bm25_create(table_name, column_name, statistic_name);. It will create a materilized view to record the stats.
• Generate document sparse vector by bm25_document_to_svector(statistic_name, passage)
• For query, generate query sparse vector bm25_query_to_svector(statistic_name, query)
• Calculate the score by dot product between the query sparse vector and the document sparse vector
• Currently we use huggingface tokenizer with bert-base-uncased vocabulary set to tokenize words. Might support more configuration on tokenizer in the future.

Install

CREATE EXTENSION pg_bestmatch;
SET search_path TO public, bm_catalog;

Example

Here is an example workflow demonstrating the usage of this extension with the example of Stanford LoCo benchmark.

0. Load the dataset. Here is a script for you if you want to experience pg_bestmatch with the dataset.

wget https://huggingface.co/api/datasets/hazyresearch/LoCoV1-Documents/parquet/default/test/0.parquet -O documents.parquet
wget https://huggingface.co/api/datasets/hazyresearch/LoCoV1-Queries/parquet/default/test/0.parquet -O queries.parquet

import pandas as pd
from sqlalchemy import create_engine
import numpy as np
from psycopg2.extensions import register_adapter, AsIs

def adapter_numpy_float64(numpy_float64):
    return AsIs(numpy_float64)

def adapter_numpy_int64(numpy_int64):
    return AsIs(numpy_int64)

def adapter_numpy_float32(numpy_float32):
    return AsIs(numpy_float32)

def adapter_numpy_int32(numpy_int32):
    return AsIs(numpy_int32)

def adapter_numpy_array(numpy_array):
    return AsIs(tuple(numpy_array))

register_adapter(np.float64, adapter_numpy_float64)
register_adapter(np.int64, adapter_numpy_int64)
register_adapter(np.float32, adapter_numpy_float32)
register_adapter(np.int32, adapter_numpy_int32)
register_adapter(np.ndarray, adapter_numpy_array)

db_url = "postgresql://localhost:5432/pg_bestmatch_test"
engine = create_engine(db_url)

def load_documents():
    df = pd.read_parquet("documents.parquet")
    df.to_sql("documents", engine, if_exists='replace', index=False)

def load_queries():
    df = pd.read_parquet("queries.parquet")
    df['answer_pids'] = df['answer_pids'].apply(lambda x: str(x[0]))    
    df.to_sql("queries", engine, if_exists='replace', index=False)

load_documents()
load_queries()

1. Create BM25 statistics for the documents table.

SELECT bm25_create('documents', 'passage', 'documents_passage_bm25', 0.75, 1.2);

2. Add an embedding column to the documents and queries tables and update the embeddings for documents and queries.

ALTER TABLE documents ADD COLUMN embedding svector; -- for pgvecto.rs users
ALTER TABLE documents ADD COLUMN embedding sparsevec; -- for pgvector users

UPDATE documents SET embedding = bm25_document_to_svector('documents_passage_bm25', passage)::svector; -- for pgvecto.rs users
UPDATE documents SET embedding = bm25_document_to_svector('documents_passage_bm25', passage, 'pgvector')::sparsevec; -- for pgvector users

3. (Optional) Create a vector index on the sparse vector column.

CREATE INDEX ON documents USING vectors (embedding svector_dot_ops); -- for pgvecto.rs users
CREATE INDEX ON documents USING ivfflat (embedding sparsevec_ip_ops); -- for pgvector users

4. Perform a vector search to find the most relevant documents for each query.

ALTER TABLE queries ADD COLUMN embedding svector; -- for pgvecto.rs users
ALTER TABLE queries ADD COLUMN embedding sparsevec; -- for pgvector users

UPDATE queries SET embedding = bm25_query_to_svector('documents_passage_bm25', query)::svector; -- for pgvecto.rs users
UPDATE queries SET embedding = bm25_query_to_svector('documents_passage_bm25', query, 'pgvector')::sparsevec; -- for pgvector users

SELECT sum((array[answer_pids] = array(SELECT pid FROM documents WHERE queries.dataset = documents.dataset ORDER BY queries.embedding <#> documents.embedding LIMIT 1))::int) FROM queries;

This workflow showcases how to leverage BM25 text queries and vector search in PostgreSQL using this extension. The Top 1 recall of BM25 on this dataset is 0.77. If you reproduce the result, your operations are correct.

Comparison with pg_search

• pg_bestmatch.rs only provides methods for generating sparse vectors and does not support index-based search (which can be achieved by pgvecto.rs or pgvector).
• pg_search performs BM25 retrieval via the external tantivy engine, which may have limitations when combined with transactions, filters, or JOIN operations. Since pg_bestmatch.rs is entirely native to Postgres, it offers full compatibility with these operations inside postgres.

Reference

• tokenize
  • Description: Tokenizes an input string into individual tokens.
  • Example:

    SELECT tokenize('i have an apple'); -- result: {i,have,an,apple}
    

• bm25_create
  • Description: Creates BM25 statistics for a specified table and column.
  • Usage:

    SELECT bm25_create('documents', 'passage', 'documents_passage_bm25');
    

  • Parameters:
    • table_name: Name of the table.
    • column_name: Name of the column.
    • stat_name: Name of the BM25 statistics.
    • b: BM25 parameter (default 0.75).
    • k: BM25 parameter (default 1.2).
• bm25_refresh
  • Description: Updates the BM25 statistics to reflect any changes in the underlying data.
  • Usage:

    SELECT bm25_refresh('documents_passage_bm25');
    

  • Parameters:
    • stat_name: Name of the BM25 statistics to update.
• bm25_drop
  • Description: Deletes the BM25 statistics for a specified table and column.
  • Usage:

    SELECT bm25_drop('documents_passage_bm25');
    

  • Parameters:
    • stat_name: Name of the BM25 statistics to delete.
• bm25_document_to_svector
  • Description: Converts document text into a sparse vector representation.
  • Usage:

    SELECT bm25_document_to_svector('documents_passage_bm25', 'document_text');
    

  • Parameters:
    • stat_name: Name of the BM25 statistics.
    • document_text: The text of the document.
    • style: Emits pgvecto.rs-style sparse vector or pgvector-style sparse vector.
• bm25_query_to_svector
  • Description: Converts query text into a sparse vector representation.
  • Usage:

    SELECT bm25_query_to_svector('documents_passage_bm25', 'We begin, as always, with the text.');
    

  • Parameters:
    • stat_name: Name of the BM25 statistics.
    • query_text: The text of the query.
    • style: Emits pgvecto.rs-style sparse vector or pgvector-style sparse vector.

7 - vchord_bm25

Overview

PIGSTY 3rd Party Extension: vchord_bm25 : A postgresql extension for bm25 ranking algorithm

Information

• Extension ID: 2150
• Extension Name: vchord_bm25
• Package Name: vchord_bm25
• Category: FTS
• License: AGPLv3
• Website: https://github.com/tensorchord/VectorChord-bm25
• Language: Rust
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 0.1.0
• Postgres Support: 17,16,15,14
• Need Load: Explicit Loading Required
• Need DDL: Need CREATE EXTENSION DDL
• Relocatable: Can be installed into other schemas
• Trusted: Untrusted, Require Superuser to Create
• Schemas: bm25_catalog
• Requires: N/A

RPM / DEB

• RPM Repo: PIGSTY
• RPM Name: vchord_bm25_$v
• RPM Ver : 0.1.0
• RPM Deps: N/A
• DEB Repo: PIGSTY
• DEB Name: postgresql-$v-vchord-bm25
• DEB Ver : 0.1.0
• DEB Deps: N/A

Packages

Installation

Install vchord_bm25 via the pig CLI tool:

pig ext install vchord_bm25

Install vchord_bm25 via Pigsty playbook:

./pgsql.yml -t pg_extension -e '{"pg_extensions": ["vchord_bm25"]}' # -l <cls>

Install vchord_bm25 RPM from YUM repo directly:

dnf install vchord_bm25_17;
dnf install vchord_bm25_16;
dnf install vchord_bm25_15;
dnf install vchord_bm25_14;

Install vchord_bm25 DEB from APT repo directly:

apt install postgresql-17-vchord-bm25;
apt install postgresql-16-vchord-bm25;
apt install postgresql-15-vchord-bm25;
apt install postgresql-14-vchord-bm25;

Extension vchord_bm25 has to be added to shared_preload_libraries

shared_preload_libraries = 'vchord_bm25'; # add to pg cluster config

Enable vchord_bm25 extension on PostgreSQL cluster：

CREATE EXTENSION vchord_bm25;

8 - hunspell_cs_cz

Overview

PIGSTY 3rd Party Extension: hunspell_cs_cz : Czech Hunspell Dictionary

Information

• Extension ID: 2170
• Extension Name: hunspell_cs_cz
• Package Name: hunspell
• Category: FTS
• License: PostgreSQL
• Website: https://github.com/postgrespro/hunspell_dicts
• Language: Data
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 1.0
• Postgres Support: 17,16,15,14,13
• Need Load: Shared library do not need explicit loading
• Need DDL: Need CREATE EXTENSION DDL
• Relocatable: Can not install to arbitrary schema
• Trusted: Untrusted, Require Superuser to Create
• Schemas: N/A
• Requires: N/A

RPM / DEB

• RPM Repo: PIGSTY
• RPM Name: hunspell_cs_cz_$v
• RPM Ver : 1.0
• RPM Deps: N/A
• DEB Repo: PIGSTY
• DEB Name: postgresql-$v-hunspell-cs-cz
• DEB Ver : 1.0
• DEB Deps: N/A

Packages

Installation

Install hunspell_cs_cz via the pig CLI tool:

pig ext install hunspell_cs_cz

Install hunspell_cs_cz via Pigsty playbook:

./pgsql.yml -t pg_extension -e '{"pg_extensions": ["hunspell_cs_cz"]}' # -l <cls>

Install hunspell_cs_cz RPM from YUM repo directly:

dnf install hunspell_cs_cz_17;
dnf install hunspell_cs_cz_16;
dnf install hunspell_cs_cz_15;
dnf install hunspell_cs_cz_14;
dnf install hunspell_cs_cz_13;

Install hunspell_cs_cz DEB from APT repo directly:

apt install postgresql-17-hunspell-cs-cz;
apt install postgresql-16-hunspell-cs-cz;
apt install postgresql-15-hunspell-cs-cz;
apt install postgresql-14-hunspell-cs-cz;
apt install postgresql-13-hunspell-cs-cz;

Enable hunspell_cs_cz extension on PostgreSQL cluster：

CREATE EXTENSION hunspell_cs_cz;

9 - hunspell_de_de

Overview

PIGSTY 3rd Party Extension: hunspell_de_de : German Hunspell Dictionary

Information

• Extension ID: 2171
• Extension Name: hunspell_de_de
• Package Name: hunspell
• Category: FTS
• License: PostgreSQL
• Website: https://github.com/postgrespro/hunspell_dicts
• Language: Data
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 1.0
• Postgres Support: 17,16,15,14,13
• Need Load: Shared library do not need explicit loading
• Need DDL: Need CREATE EXTENSION DDL
• Relocatable: Can not install to arbitrary schema
• Trusted: Untrusted, Require Superuser to Create
• Schemas: N/A
• Requires: N/A

RPM / DEB

• RPM Repo: PIGSTY
• RPM Name: hunspell_de_de_$v
• RPM Ver : 1.0
• RPM Deps: N/A
• DEB Repo: PIGSTY
• DEB Name: postgresql-$v-hunspell-de-de
• DEB Ver : 1.0
• DEB Deps: N/A

Packages

Installation

Install hunspell_de_de via the pig CLI tool:

pig ext install hunspell_de_de

Install hunspell_de_de via Pigsty playbook:

./pgsql.yml -t pg_extension -e '{"pg_extensions": ["hunspell_de_de"]}' # -l <cls>

Install hunspell_de_de RPM from YUM repo directly:

dnf install hunspell_de_de_17;
dnf install hunspell_de_de_16;
dnf install hunspell_de_de_15;
dnf install hunspell_de_de_14;
dnf install hunspell_de_de_13;

Install hunspell_de_de DEB from APT repo directly:

apt install postgresql-17-hunspell-de-de;
apt install postgresql-16-hunspell-de-de;
apt install postgresql-15-hunspell-de-de;
apt install postgresql-14-hunspell-de-de;
apt install postgresql-13-hunspell-de-de;

Enable hunspell_de_de extension on PostgreSQL cluster：

CREATE EXTENSION hunspell_de_de;

10 - hunspell_en_us

Overview

PIGSTY 3rd Party Extension: hunspell_en_us : en_US Hunspell Dictionary

Information

• Extension ID: 2172
• Extension Name: hunspell_en_us
• Package Name: hunspell
• Category: FTS
• License: PostgreSQL
• Website: https://github.com/postgrespro/hunspell_dicts
• Language: Data
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 1.0
• Postgres Support: 17,16,15,14,13
• Need Load: Shared library do not need explicit loading
• Need DDL: Need CREATE EXTENSION DDL
• Relocatable: Can not install to arbitrary schema
• Trusted: Untrusted, Require Superuser to Create
• Schemas: N/A
• Requires: N/A

RPM / DEB

• RPM Repo: PIGSTY
• RPM Name: hunspell_en_us_$v
• RPM Ver : 1.0
• RPM Deps: N/A
• DEB Repo: PIGSTY
• DEB Name: postgresql-$v-hunspell-en-us
• DEB Ver : 1.0
• DEB Deps: N/A