parray_gin
Overview
| Package | Version | Category | License | Language |
|---|---|---|---|---|
parray_gin | 1.5.0 | FUNC | PostgreSQL | C |
| ID | Extension | Bin | Lib | Load | Create | Trust | Reloc | Schema |
|---|---|---|---|---|---|---|---|---|
| 4860 | parray_gin | No | Yes | No | Yes | No | Yes | - |
PGXN dist name and PostgreSQL extension name are both parray_gin; Pigsty packages are built for PG 14-18.
Version
| Type | Repo | Version | PG Ver | Package | Deps |
|---|---|---|---|---|---|
| EXT | PIGSTY | 1.5.0 | 1817161514 | parray_gin | - |
| RPM | PIGSTY | 1.5.0 | 1817161514 | parray_gin_$v | - |
| DEB | PIGSTY | 1.5.0 | 1817161514 | postgresql-$v-parray-gin | - |
Build
You can build the RPM / DEB packages for parray_gin using pig build:
Install
You can install parray_gin directly. First, make sure the PGDG and PIGSTY repositories are added and enabled:
Install the extension using pig or apt/yum/dnf:
Create Extension:
Usage
- Sources: README, reference doc
parray_gin adds a GIN operator class for text[] plus strict and partial-match operators. Upstream describes it as trigram-based array indexing built on pg_trgm trigram decomposition.
Create The Extension And Index
Indexed Operators
The reference doc says parray_gin_ops can support these operators:
@>: strict contains.<@: strict contained-by.@@>: partial contains, where array elements may useLIKEpatterns.<@@: partial contained-by.
Examples:
Matching Behavior
Strict matching requires array-item equality. Partial matching allows patterns such as 'foo%' or '%oo%'. Because the trigram index can return false positives, the docs note that matches are rechecked after index lookup.
Caveats
The README says support extends through PostgreSQL 18, while the reference document still says 9.1-14. The operator and opclass behavior is consistent across both docs, but the version note is not fully synchronized upstream.
Was this page helpful?
Thanks—your feedback helps us improve this page.
What got in the way? (optional)