lolor
Overview
| Package | Version | Category | License | Language |
|---|---|---|---|---|
lolor | 1.2.2 | ETL | PostgreSQL | C |
| ID | Extension | Bin | Lib | Load | Create | Trust | Reloc | Schema |
|---|---|---|---|---|---|---|---|---|
| 9580 | lolor | No | Yes | No | Yes | Yes | No | lolor |
works on pgedge kernel fork. Requires lolor.node
Version
| Type | Repo | Version | PG Ver | Package | Deps |
|---|---|---|---|---|---|
| EXT | PIGSTY | 1.2.2 | 1817161514 | lolor | - |
| RPM | PIGSTY | 18.4 | 1817161514 | pgedge-$v | - |
| DEB | PIGSTY | 18.4 | 1817161514 | pgedge-$v | - |
Build
You can build the RPM / DEB packages for lolor using pig build:
Install
You can install lolor 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
lolor: Logical-replication-friendly replacement for PostgreSQL large objects
Makes PostgreSQL large objects compatible with logical replication by storing them in non-catalog tables.
Enabling
Configure the node identifier in postgresql.conf:
Optionally adjust the search path:
Large Object Operations
Once installed, the standard lo_* functions are redirected to use lolor’s tables:
Replication Setup
Add lolor tables to your replication set:
Internal Tables
The extension manages large objects in:
lolor.pg_largeobject- stores object data chunkslolor.pg_largeobject_metadata- stores object metadata
Limitations
- Native PostgreSQL large object functionality cannot be used while lolor is active
- Migration of existing native large objects to lolor is not supported
ALTER LARGE OBJECT,GRANT ON LARGE OBJECT,COMMENT ON LARGE OBJECT, andREVOKE ON LARGE OBJECTare not supported- Requires PostgreSQL 16 or newer
Was this page helpful?
Thanks—your feedback helps us improve this page.
What got in the way? (optional)