Category: TYPE

• 1: prefix
• 2: semver
• 3: unit
• 4: pgpdf
• 5: pglite_fusion
• 6: md5hash
• 7: asn1oid
• 8: roaringbitmap
• 9: pgfaceting
• 10: pg_sphere
• 11: country
• 12: pg_xenophile
• 13: currency
• 14: collection
• 15: pgmp
• 16: numeral
• 17: pg_rational
• 18: uint
• 19: uint128
• 20: hashtypes
• 21: ip4r
• 22: pg_duration
• 23: uri
• 24: emailaddr
• 25: acl
• 26: debversion
• 27: pg_rrule
• 28: timestamp9
• 29: chkpass
• 30: isn
• 31: seg
• 32: cube
• 33: ltree
• 34: hstore
• 35: citext
• 36: xml2

1 - prefix

Overview

PGDG 1st Party Extension: pg_prefix : Prefix Range module for PostgreSQL

Information

• Extension ID: 3500
• Extension Name: prefix
• Package Name: pg_prefix
• Category: TYPE
• License: PostgreSQL
• Website: https://github.com/dimitri/prefix
• Language: C
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 1.2.10
• 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: prefix_$v*
• RPM Ver : 1.2.10
• RPM Deps: N/A
• DEB Repo: PGDG
• DEB Name: postgresql-$v-prefix
• DEB Ver : 1.2.10
• DEB Deps: N/A

Availability

Installation

Install prefix via the pig CLI tool:

pig ext install pg_prefix; 	# Extension Name
pig ext install prefix; 	# normalized package name

Install pg_prefix via Pigsty playbook:

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

Install pg_prefix RPM from YUM repo directly:

dnf install prefix_17*;
dnf install prefix_16*;
dnf install prefix_15*;
dnf install prefix_14*;
dnf install prefix_13*;

Install pg_prefix DEB from APT repo directly:

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

Create prefix extension on PostgreSQL cluster:

CREATE EXTENSION prefix;

2 - semver

Overview

PGDG 1st Party Extension: pg_semver : Semantic version data type

Information

• Extension ID: 3510
• Extension Name: semver
• Package Name: pg_semver
• Category: TYPE
• License: PostgreSQL
• Website: https://github.com/theory/pg-semver
• Language: C
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 0.40.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: PGDG
• RPM Name: semver_$v*
• RPM Ver : 0.32.1
• RPM Deps: N/A
• DEB Repo: PGDG
• DEB Name: postgresql-$v-semver
• DEB Ver : 0.40.0
• DEB Deps: N/A

Availability

Installation

Install semver via the pig CLI tool:

pig ext install pg_semver; 	# Extension Name
pig ext install semver; 	# normalized package name

Install pg_semver via Pigsty playbook:

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

Install pg_semver RPM from YUM repo directly:

dnf install semver_17*;
dnf install semver_16*;
dnf install semver_15*;
dnf install semver_14*;
dnf install semver_13*;

Install pg_semver DEB from APT repo directly:

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

Create semver extension on PostgreSQL cluster:

CREATE EXTENSION semver;

3 - unit

Overview

PGDG 1st Party Extension: pgunit : SI units extension

Information

• Extension ID: 3520
• Extension Name: unit
• Package Name: pgunit
• Category: TYPE
• License: GPLv2
• Website: https://github.com/df7cb/postgresql-unit
• Language: C
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 7.10
• Postgres Support: 17,16,15,14,13
• Need Load: Shared library do not need explicit loading
• Need DDL: Need CREATE EXTENSION DDL
• Relocatable: Can be installed into other schemas
• Trusted: Untrusted, Require Superuser to Create
• Schemas: N/A
• Requires: plpgsql

RPM / DEB

• RPM Repo: PGDG
• RPM Name: postgresql-unit_$v*
• RPM Ver : 7.10
• RPM Deps: N/A
• DEB Repo: PGDG
• DEB Name: postgresql-$v-unit
• DEB Ver : 7.10
• DEB Deps: N/A

Availability

Installation

Install unit via the pig CLI tool:

pig ext install pgunit; 	# Extension Name
pig ext install unit; 	# normalized package name

Install pgunit via Pigsty playbook:

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

Install pgunit RPM from YUM repo directly:

dnf install postgresql-unit_17*;
dnf install postgresql-unit_16*;
dnf install postgresql-unit_15*;
dnf install postgresql-unit_14*;
dnf install postgresql-unit_13*;

Install pgunit DEB from APT repo directly:

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

Create unit extension on PostgreSQL cluster:

CREATE EXTENSION unit CASCADE;

4 - pgpdf

Overview

PIGSTY 3rd Party Extension: pgpdf : PDF type with meta admin & Full-Text Search

Information

• Extension ID: 3530
• Extension Name: pgpdf
• Package Name: pgpdf
• Category: TYPE
• License: GPLv3
• Website: https://github.com/Florents-Tselai/pgpdf
• Language: C
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 0.1.0
• Postgres Support: 17,16,15,14,13
• Need Load: Explicit Loading Required
• 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: pgpdf_$v*
• RPM Ver : 0.1.0
• RPM Deps: N/A
• DEB Repo: PIGSTY
• DEB Name: postgresql-$v-pgpdf
• DEB Ver : 0.1.0
• DEB Deps: N/A

Availability

Installation

Install pgpdf via the pig CLI tool:

pig ext install pgpdf

Install pgpdf via Pigsty playbook:

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

Install pgpdf RPM from YUM repo directly:

dnf install pgpdf_17*;
dnf install pgpdf_16*;
dnf install pgpdf_15*;
dnf install pgpdf_14*;
dnf install pgpdf_13*;

Install pgpdf DEB from APT repo directly:

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

Extension pgpdf has to be loaded via shared_preload_libraries

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

Create pgpdf extension on PostgreSQL cluster:

CREATE EXTENSION pgpdf;

Usage

The actual PDF parsing is done by poppler.

This allows you to work with PDFs in an ACID-compliant way. The usual alternative relies on external scripts or services which can easily make your data ingestion pipeline brittle and leave your raw data out-of-sync.

• Full Text Search on PDFs With Postgres
• pgpdf: pdf type for Postgres

Download some PDFs.

wget https://wiki.postgresql.org/images/e/ea/PostgreSQL_Introduction.pdf -O /tmp/pgintro.pdf
wget https://pdfobject.com/pdf/sample.pdf -O /tmp/sample.pdf

You can create a pdf type, by casting either a text filepath or bytea column.

CREATE EXTENSION pgpdf;
SELECT '/tmp/pgintro.pdf'::pdf;

                                       pdf                                        
----------------------------------------------------------------------------------
 PostgreSQL Introduction                                                         +
 Digoal.Zhou                                                                     +
 7/20/2011Catalog                                                                +
  PostgreSQL Origin 

If you don’t have the PDF file in your filesystem, but have already stored its content in a bytea column, you can just cast it to pdf.

SELECT pg_read_binary_file('/tmp/pgintro.pdf')::bytea::pdf;

Examples

Create a table with a pdf column:

CREATE TABLE pdfs(name text primary key, doc pdf);

INSERT INTO pdfs VALUES ('pgintro', '/tmp/pgintro.pdf');
INSERT INTO pdfs VALUES ('pgintro', '/tmp/sample.pdf');

Parsing and validation should happen automatically. The files will be read from the disk only once!

[!NOTE] The filepath should be accessible by the postgres process / user! That’s different than the user running psql. If you don’t understand what this means, as your DBA!

String Functions and Operators

Standard Postgres String Functions and Operators should work as usual:

SELECT 'Below is the PDF we received ' || '/tmp/pgintro.pdf'::pdf;

SELECT upper('/tmp/pgintro.pdf'::pdf::text);

SELECT name
FROM pdfs
WHERE doc::text LIKE '%Postgres%';

Full-Text Search (FTS)

You can also perform full-text search (FTS), since you can work on a pdf file like normal text.

SELECT '/tmp/pgintro.pdf'::pdf::text @@ to_tsquery('postgres');

 ?column? 
----------
 t
(1 row)

SELECT '/tmp/pgintro.pdf'::pdf::text @@ to_tsquery('oracle');

 ?column? 
----------
 f
(1 row)

Document similarity with pg_trgm

You can use pg_trgm to get the similarity between two documents:

CREATE EXTENSION pg_trgm;

SELECT similarity('/tmp/pgintro.pdf'::pdf::text, '/tmp/sample.pdf'::pdf::text);

Metadata

The following functions are available:

• pdf_title(pdf) → text

• pdf_author(pdf) → text

• pdf_num_pages(pdf) → integer

  Total number of pages in the document

• pdf_page(pdf, integer) → text

  Get the i-th page as text

• pdf_creator(pdf) → text

• pdf_keywords(pdf) → text

• pdf_metadata(pdf) → text

• pdf_version(pdf) → text

• pdf_subject(pdf) → text

• pdf_creation(pdf) → timestamp

• pdf_modification(pdf) → timestamp

SELECT pdf_title('/tmp/pgintro.pdf');

        pdf_title        
-------------------------
 PostgreSQL Introduction
(1 row)

SELECT pdf_author('/tmp/pgintro.pdf');

 pdf_author 
------------
 周正中
(1 row)

Getting a subset of pages

SELECT pdf_num_pages('/tmp/pgintro.pdf');

 pdf_num_pages 
---------------
            24
(1 row)

SELECT pdf_page('/tmp/pgintro.pdf', 1);

           pdf_page           
------------------------------
 Catalog                     +
  PostgreSQL Origin         +
  Layout                    +
  Features                  +
  Enterprise Class Attribute+
  Case
(1 row)

SELECT pdf_subject('/tmp/pgintro.pdf');

 pdf_subject 
-------------
 
(1 row)

SELECT pdf_creation('/tmp/pgintro.pdf');

       pdf_creation       
--------------------------
 Wed Jul 20 11:13:37 2011
(1 row)

SELECT pdf_modification('/tmp/pgintro.pdf');

     pdf_modification     
--------------------------
 Wed Jul 20 11:13:37 2011
(1 row)

SELECT pdf_creator('/tmp/pgintro.pdf');

            pdf_creator             
------------------------------------
 Microsoft® Office PowerPoint® 2007
(1 row)

SELECT pdf_metadata('/tmp/pgintro.pdf');

 pdf_metadata 
--------------
 
(1 row)

SELECT pdf_version('/tmp/pgintro.pdf');

 pdf_version 
-------------
 PDF-1.5
(1 row)

Installation

Install poppler dependencies

Linux

sudo apt install -y libpoppler-glib-dev pkg-config

Homebrew/MacOS

brew install poppler pkgconf

cd /tmp
git clone https://github.com/Florents-Tselai/pgpdf.git
cd pgpdf
make
make install # may need sudo

After the installation, in a session:

CREATE EXTENSION pgpdf;

Docker

Get the Docker image with:

docker pull florents/pgpdf:pg17

This adds pgpdf to the Postgres image (replace 17 with your Postgres server version, and run it the same way).

Run the image in a container.

docker run --name pgpdf -p 5432:5432 -e POSTGRES_PASSWORD=pass florents/pgpdf:pg17

Through another terminal, connect to the running server (container).

PGPASSWORD=pass psql -h localhost -p 5432 -U postgres

[!WARNING] Reading arbitrary binary data (PDF) into your database can pose security risks. Only use this for files you trust.

5 - pglite_fusion

Overview

PIGSTY 3rd Party Extension: pglite_fusion : Embed an SQLite database in your PostgreSQL table

Information

• Extension ID: 3540
• Extension Name: pglite_fusion
• Package Name: pglite_fusion
• Category: TYPE
• License: MIT
• Website: https://github.com/frectonz/pglite-fusion
• Language: Rust
• Extra Tags: pgrx
• Comment: N/A

Metadata

• Latest Version: 0.0.3
• 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: N/A
• Requires: N/A

RPM / DEB

• RPM Repo: PIGSTY
• RPM Name: pglite_fusion_$v
• RPM Ver : 0.0.3
• RPM Deps: N/A
• DEB Repo: PIGSTY
• DEB Name: postgresql-$v-pglite-fusion
• DEB Ver : 0.0.3
• DEB Deps: N/A

Availability

Installation

Install pglite_fusion via the pig CLI tool:

pig ext install pglite_fusion

Install pglite_fusion via Pigsty playbook:

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

Install pglite_fusion RPM from YUM repo directly:

dnf install pglite_fusion_17;
dnf install pglite_fusion_16;
dnf install pglite_fusion_15;
dnf install pglite_fusion_14;
dnf install pglite_fusion_13;

Install pglite_fusion DEB from APT repo directly:

apt install postgresql-17-pglite-fusion;
apt install postgresql-16-pglite-fusion;
apt install postgresql-15-pglite-fusion;
apt install postgresql-14-pglite-fusion;
apt install postgresql-13-pglite-fusion;

Extension pglite_fusion has to be loaded via shared_preload_libraries

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

Create pglite_fusion extension on PostgreSQL cluster:

CREATE EXTENSION pglite_fusion;

Usage

https://github.com/frectonz/pglite-fusion/blob/main/README.md

Here’s some demo usage.

-- Load PG extension
CREATE EXTENSION pglite_fusion;

-- Create a table with an SQLite column
CREATE TABLE people (
                        name     TEXT NOT NULL,
                        database SQLITE DEFAULT init_sqlite('CREATE TABLE todos (task TEXT)')
);

-- Insert a row into the people table
INSERT INTO people VALUES ('frectonz');

-- Create a todo for "frectonz"
UPDATE people
SET database = execute_sqlite(
        database,
        'INSERT INTO todos VALUES (''solve multitenancy'')'
               )
WHERE name = 'frectonz';

-- Create a todo for "frectonz"
UPDATE people
SET database = execute_sqlite(
        database,
        'INSERT INTO todos VALUES (''buy milk'')'
               )
WHERE name = 'frectonz';

-- Fetch frectonz's info
SELECT
    name,
    (
        SELECT json_agg(get_sqlite_text(sqlite_row, 0))
        FROM query_sqlite(
                database,
                'SELECT * FROM todos'
             )
    ) AS todos
FROM
    people
WHERE
    name = 'frectonz';

API Doc

empty_sqlite

Creates an empty SQLite database and returns it as a binary object. This can be used to initialize an empty SQLite database in a PostgreSQL column.

Example Usage:

SELECT empty_sqlite();

query_sqlite

Executes a SQL query on a SQLite database stored as a binary object and returns the result as a table of JSON-encoded rows. This function is useful for querying SQLite databases stored in PostgreSQL columns.

Parameters:

• sqlite: The SQLite database to query, stored as a binary object.
• query: The SQL query string to execute on the SQLite database.

Example Usage:

SELECT * FROM query_sqlite(
        database,
        'SELECT * FROM todos'
              );

execute_sqlite

Executes a SQL statement (such as INSERT, UPDATE, or DELETE) on a SQLite database stored as a binary object. The updated SQLite database is returned as a binary object, allowing further operations on it.

Parameters:

• sqlite: The SQLite database to execute the SQL query on, stored as a binary object.
• query: The SQL statement to execute on the SQLite database.

Example Usage:

UPDATE people
SET database = execute_sqlite(
        database,
        'INSERT INTO todos VALUES (''solve multitenancy'')'
               )
WHERE name = 'frectonz';

init_sqlite

Creates an SQLite database with an initialization query already applied on it. This can be used to initialize a SQLite database with the expected tables already created.

Parameters:

• query: The SQL statement to execute on the SQLite database.

Example Usage:

CREATE TABLE people (
                        name     TEXT NOT NULL,
                        database SQLITE DEFAULT init_sqlite('CREATE TABLE todos (task TEXT)')
);

get_sqlite_text

Extracts a text value from a specific column in a row returned by query_sqlite. Use this function to retrieve text values from query results.

Parameters:

• sqlite_row: A row from the results of query_sqlite.
• index: The index of the column to extract from the row.

Example Usage:

SELECT get_sqlite_text(sqlite_row, 0)
FROM query_sqlite(database, 'SELECT * FROM todos');

get_sqlite_integer

Extracts an integer value from a specific column in a row returned by query_sqlite. Use this function to retrieve integer values from query results.

Parameters:

• sqlite_row: A row from the results of query_sqlite.
• index: The index of the column to extract from the row.

Example Usage:

SELECT get_sqlite_integer(sqlite_row, 1)
FROM query_sqlite(database, 'SELECT * FROM todos');

get_sqlite_real

Extracts a real (floating-point) value from a specific column in a row returned by query_sqlite. Use this function to retrieve real number values from query results.

Parameters:

• sqlite_row: A row from the results of query_sqlite.
• index: The index of the column to extract from the row.

Example Usage:

SELECT get_sqlite_real(sqlite_row, 2)
FROM query_sqlite(database, 'SELECT * FROM todos');

6 - md5hash

Overview

PIGSTY 3rd Party Extension: md5hash : type for storing 128-bit binary data inline

Information

• Extension ID: 3550
• Extension Name: md5hash
• Package Name: md5hash
• Category: TYPE
• License: BSD 2
• Website: https://github.com/tvondra/md5hash
• Language: C
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 1.0.1
• 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: md5hash_$v*
• RPM Ver : 1.0.1
• RPM Deps: N/A
• DEB Repo: PIGSTY
• DEB Name: postgresql-$v-md5hash
• DEB Ver : 1.0.1
• DEB Deps: N/A

Availability

Installation

Install md5hash via the pig CLI tool:

pig ext install md5hash

Install md5hash via Pigsty playbook:

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

Install md5hash RPM from YUM repo directly:

dnf install md5hash_17*;
dnf install md5hash_16*;
dnf install md5hash_15*;
dnf install md5hash_14*;
dnf install md5hash_13*;

Install md5hash DEB from APT repo directly:

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

Create md5hash extension on PostgreSQL cluster:

CREATE EXTENSION md5hash;

7 - asn1oid

Overview

MIXED 3rd Party Extension: asn1oid : asn1oid extension

Information

• Extension ID: 3560
• Extension Name: asn1oid
• Package Name: asn1oid
• Category: TYPE
• License: GPLv3
• Website: https://github.com/df7cb/pgsql-asn1oid
• Language: C
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 1.6
• 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: asn1oid_$v*
• RPM Ver : 1.5
• RPM Deps: N/A
• DEB Repo: PGDG
• DEB Name: postgresql-$v-asn1oid
• DEB Ver : 1.6
• DEB Deps: N/A

Availability

Installation

Install asn1oid via the pig CLI tool:

pig ext install asn1oid

Install asn1oid via Pigsty playbook:

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

Install asn1oid RPM from YUM repo directly:

dnf install asn1oid_17*;
dnf install asn1oid_16*;
dnf install asn1oid_15*;
dnf install asn1oid_14*;
dnf install asn1oid_13*;

Install asn1oid DEB from APT repo directly:

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

Create asn1oid extension on PostgreSQL cluster:

CREATE EXTENSION asn1oid;

8 - roaringbitmap

Overview

MIXED 3rd Party Extension: roaringbitmap : support for Roaring Bitmaps

Information

• Extension ID: 3570
• Extension Name: roaringbitmap
• Package Name: roaringbitmap
• Category: TYPE
• License: Apache-2.0
• Website: https://github.com/ChenHuajun/pg_roaringbitmap
• Language: C
• Extra Tags: N/A
• Comment: N/A

Metadata

• Latest Version: 0.5.4
• 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: pg_roaringbitmap_$v*
• RPM Ver : 0.5
• RPM Deps: N/A
• DEB Repo: PGDG
• DEB Name: postgresql-$v-roaringbitmap
• DEB Ver : 0.5
• DEB Deps: N/A

Availability

Installation

Install roaringbitmap via the pig CLI tool:

pig ext install roaringbitmap

Install roaringbitmap via Pigsty playbook:

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

Install roaringbitmap RPM from YUM repo directly:

dnf install pg_roaringbitmap_17*;
dnf install pg_roaringbitmap_16*;
dnf install pg_roaringbitmap_15*;
dnf install pg_roaringbitmap_14*;
dnf install pg_roaringbitmap_13*;

Install roaringbitmap DEB from APT repo directly:

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

Create roaringbitmap extension on PostgreSQL cluster:

CREATE EXTENSION roaringbitmap;

9 - pgfaceting

Overview

MIXED 3rd Party Extension: pgfaceting : fast faceting queries using an inverted index

Information

• Extension ID: 3580
• Extension Name: pgfaceting
• Package Name: pgfaceting
• Category: TYPE
• License: BSD 3
• Website: https://github.com/cybertec-postgresql/pgfaceting
• Language: SQL
• Extra Tags: N/A
• Comment: N/A