update extension docs

Author: Vonng

content/_index.md

@@ -12,12 +12,12 @@ comment: false
 
 PGEXT.CLOUD provides three things to help you harness the synergistic superpower of the PostgreSQL extensions ecosystem:
 
-- [**Catalog**](/list) : Find the extension you need, with unparalleled [**461**](/e/) extensions included
+- [**Catalog**](/list) : Find the extension you need, with unparalleled [**464**](/e/) extensions included
 - [**Repository**](/repo) : Get pre-built RPM/DEB packages on **14** mainstream [**Linux Distributions**](/os)
 - [**PIG Package Manager**](/pig/) : The Missing Package Manager for PostgreSQL & Extension Ecosystem
 
 {{< cards cols=4 >}}  
-  {{< card link="/list" title="Extension Catalog" icon="clipboard-list" subtitle="The complete list of 461 available PostgreSQL extensions" >}}
+  {{< card link="/list" title="Extension Catalog" icon="clipboard-list" subtitle="The complete list of 464 available PostgreSQL extensions" >}}
   {{< card link="/repo" title="Software Repository" icon="cube" subtitle="The APT / DNF repo that deliver PostgreSQL extensions in native Linux format" >}}
   {{< card link="/pig" title="Package Manager" icon="cash" subtitle="The missing package manager for PostgreSQL & Extensions Ecosystem" >}}
 {{< /cards >}}
@@ -37,7 +37,7 @@ pig install pg_duckdb -v 18   # e.g. install pg_duckdb extension for PG 18
 
 ## Highlights
 
-- **461 Extensions** : the largest catalog in the postgres ecosystem
+- **464 Extensions** : the largest catalog in the postgres ecosystem
 - **Linux Native** : RPM/DEB packages, properly built, freely compose
 - **Handy CLI** : pig on apt/dnf, zero‑config installs; out-of-the-box
 - **Compatibility** : PGDG‑Compliant, drop‑in with official PG kernel
@@ -128,7 +128,7 @@ Pigsty provides complete extension support on these [linux distributions](/os) m
 The **PGSTY.CLOUD** is used by some PostgreSQL Distribution Maker and Vendors to deliver PG extensions to their users and customers.
 
 {{< cards cols=1 >}}
-{{< card link="https://github.com/pgsty/pigsty"     title="Pigsty"     icon="github" subtitle="Battery-Included Local-First PostgreSQL Distribution as an Open Source RDS, with HA, PITR, IaC, Observability and 461 extensions!" >}}
+{{< card link="https://github.com/pgsty/pigsty"     title="Pigsty"     icon="github" subtitle="Battery-Included Local-First PostgreSQL Distribution as an Open Source RDS, with HA, PITR, IaC, Observability and 464 extensions!" >}}
 {{< /cards >}}
 
 {{< cards cols=2 >}}

content/_index.zh.md

@@ -199,3 +199,73 @@ pig install acl -v 14;   # install for PG 14
 ```sql
 CREATE EXTENSION acl;
 ```
+
+
+
+## Usage
+
+> [acl: access control list data type for PostgreSQL](https://github.com/arkhipov/acl)
+
+The `acl` extension provides Access Control List types for row-level security based on application users, without requiring separate database accounts.
+
+```sql
+CREATE EXTENSION acl;
+```
+
+### Data Types
+
+- **`ace`**: Standard role-based ACE using PostgreSQL OIDs
+- **`ace_int4`**: ACE with 32-bit integer identifiers
+- **`ace_int8`**: ACE with 64-bit integer identifiers
+- **`ace_uuid`**: ACE with UUID identifiers
+
+ACLs are stored as PostgreSQL arrays of ACE types (e.g., `ace[]`).
+
+### ACE Format
+
+```
+[type]/[flags]/[who]=[mask]
+```
+
+- **Type**: `a` (allow) or `d` (deny)
+- **Flags**: `i` (inherit only), `o` (object inherit), `c` (container inherit), `p` (no propagate), `h` (inherited)
+- **Who**: Role name, OID, integer, UUID, or `""` (everyone)
+- **Permissions**: `r` (read), `w` (write), `d` (delete), `c` (read ACL), `s` (write ACL), plus 16 custom permissions (0-F)
+
+### Checking Permissions
+
+```sql
+-- Check current user's access
+SELECT acl_check_access(acl_column, 'rw', false) FROM my_table;
+
+-- Check specific role
+SELECT acl_check_access(acl_column, 'r', 'username'::name, false);
+
+-- Check custom int4 roles
+SELECT acl_check_access(acl_column, 'rw', ARRAY[1001, 1002]::int4[], false);
+```
+
+### ACL Inheritance
+
+```sql
+-- Compute child ACL from parent
+SELECT acl_merge(parent_acl, child_acl, true, true);
+```
+
+### Row-Level Security Example
+
+```sql
+CREATE TABLE file_system (
+    id   int PRIMARY KEY,
+    name text,
+    acl  ace[]
+);
+
+ALTER TABLE file_system ENABLE ROW LEVEL SECURITY;
+
+CREATE POLICY read_policy ON file_system FOR SELECT TO PUBLIC
+    USING (acl_check_access(acl, 'r', false) = 'r');
+
+CREATE POLICY write_policy ON file_system FOR UPDATE TO PUBLIC
+    USING (acl_check_access(acl, 'w', false) = 'w');
+```

content/e/acl.md

@@ -90,3 +90,97 @@ pig install address_standardizer -v 14;   # install for PG 14
 ```sql
 CREATE EXTENSION address_standardizer;
 ```
+
+
+
+## Usage
+
+> [Address Standardizer: Address parsing and standardization for PostGIS](https://github.com/postgis/postgis)
+
+The Address Standardizer is a PostGIS extension that parses a single-line address string into a structured form using configurable lexicon, grammar, and rules tables. It is a more flexible alternative to the built-in `normalize_address` function in the TIGER geocoder.
+
+- [Address Standardizer Reference](https://postgis.net/docs/Extras.html#Address_Standardizer)
+
+### Setup
+
+```sql
+CREATE EXTENSION address_standardizer;
+```
+
+--------
+
+## Standardizing Addresses
+
+The core function takes an address string and three table references (lex, gaz, rules):
+
+```sql
+SELECT *
+FROM standardize_address(
+    'us_lex',        -- lexicon table
+    'us_gaz',        -- gazetteer table
+    'us_rules',      -- rules table
+    '1600 Pennsylvania Ave NW, Washington, DC 20500'
+);
+```
+
+The result contains structured fields:
+
+| Field | Description |
+|-------|-------------|
+| `building` | Building name or identifier |
+| `house_num` | Street number |
+| `predir` | Prefix direction (N, S, E, W) |
+| `qual` | Qualifier |
+| `pretype` | Prefix type |
+| `name` | Street name |
+| `suftype` | Suffix type (St, Ave, Blvd) |
+| `sufdir` | Suffix direction |
+| `ruralroute` | Rural route |
+| `extra` | Extra information |
+| `city` | City name |
+| `state` | State |
+| `country` | Country |
+| `postcode` | ZIP/postal code |
+| `box` | PO Box |
+| `unit` | Unit/apartment number |
+
+--------
+
+## Lexicon, Gazetteer, and Rules Tables
+
+The standardizer is driven by three user-configurable tables:
+
+**Lexicon (lex)** -- Maps input tokens to standardized forms and token classes:
+
+```sql
+CREATE TABLE us_lex (
+    id serial PRIMARY KEY,
+    seq integer,
+    word text,
+    stdword text,
+    token integer
+);
+```
+
+**Gazetteer (gaz)** -- Maps place names (cities, states) to standard forms:
+
+```sql
+CREATE TABLE us_gaz (
+    id serial PRIMARY KEY,
+    seq integer,
+    word text,
+    stdword text,
+    token integer
+);
+```
+
+**Rules (rules)** -- Defines grammar rules for parsing addresses:
+
+```sql
+CREATE TABLE us_rules (
+    id serial PRIMARY KEY,
+    rule text
+);
+```
+
+For US addresses, the `address_standardizer_data_us` extension provides pre-built data for these tables.

content/e/address_standardizer.md

@@ -90,3 +90,43 @@ pig install address_standardizer_data_us -v 14;   # install for PG 14
 ```sql
 CREATE EXTENSION address_standardizer_data_us;
 ```
+
+
+
+## Usage
+
+> [Address Standardizer Data US: US address data for the address_standardizer extension](https://github.com/postgis/postgis)
+
+This extension provides pre-built US lexicon, gazetteer, and rules data for use with the `address_standardizer` extension. It includes tables with common US street types, directional abbreviations, state names, and grammar rules needed to parse US addresses.
+
+- [Address Standardizer Reference](https://postgis.net/docs/Extras.html#Address_Standardizer)
+
+### Setup
+
+```sql
+CREATE EXTENSION address_standardizer_data_us;
+```
+
+This creates the `us_lex`, `us_gaz`, and `us_rules` tables in the public schema, pre-populated with US address data.
+
+--------
+
+## Using with address_standardizer
+
+Once installed, you can immediately standardize US addresses:
+
+```sql
+SELECT *
+FROM standardize_address(
+    'us_lex', 'us_gaz', 'us_rules',
+    '123 Main Street NW, Apt 4B, Springfield, IL 62704'
+);
+```
+
+The provided data covers common US address patterns including:
+
+- Street types (Street, Avenue, Boulevard, Drive, Lane, Court, etc.)
+- Directional prefixes and suffixes (North, South, N, S, NW, SE, etc.)
+- State names and abbreviations
+- Unit designators (Apt, Suite, Unit, etc.)
+- Highway designators (US, State, County, Interstate, etc.)

content/e/address_standardizer_data_us.md

@@ -44,3 +44,61 @@ width: full
 ```sql
 CREATE EXTENSION adminpack;
 ```
+
+
+
+
+## Usage
+
+> [adminpack: administrative functions for PostgreSQL](https://www.postgresql.org/docs/16/adminpack.html)
+
+The `adminpack` extension provides server-side file management and log access functions, primarily used by pgAdmin and other administration tools. All functions are restricted to superusers by default.
+
+### File Operations
+
+```sql
+-- Write text to a file (append=false: file must not exist; append=true: append)
+SELECT pg_file_write('/tmp/test.txt', 'Hello World', false);   -- returns bytes written
+
+-- Append to existing file
+SELECT pg_file_write('/tmp/test.txt', E'\nMore data', true);
+
+-- Sync file to disk
+SELECT pg_file_sync('/tmp/test.txt');
+
+-- Rename a file
+SELECT pg_file_rename('/tmp/old.txt', '/tmp/new.txt');
+
+-- Rename with archiving (moves existing newname to archive first)
+SELECT pg_file_rename('/tmp/old.txt', '/tmp/new.txt', '/tmp/archive.txt');
+
+-- Delete a file
+SELECT pg_file_unlink('/tmp/test.txt');   -- returns true on success
+```
+
+### Log File Access
+
+```sql
+-- List server log files (requires default log_filename format)
+SELECT * FROM pg_logdir_ls();
+```
+
+Returns timestamps and paths of log files from the `log_directory`.
+
+### Function Reference
+
+| Function | Returns | Description |
+|----------|---------|-------------|
+| `pg_file_write(filename, data, append)` | bigint | Write text to file; returns bytes written |
+| `pg_file_sync(filename)` | void | Flush file or directory to disk |
+| `pg_file_rename(old, new [, archive])` | boolean | Rename file, optionally archiving existing target |
+| `pg_file_unlink(filename)` | boolean | Delete a file |
+| `pg_logdir_ls()` | setof record | List log files with timestamps |
+
+### Access Control
+
+- All functions default to superuser-only access
+- Permissions can be granted via `GRANT` to non-superusers
+- File access is restricted to the database cluster directory unless the user has `pg_read_server_files` or `pg_write_server_files` roles
+
+Note: `adminpack` was removed in PostgreSQL 17. For PostgreSQL 16 and earlier only.

content/e/adminpack.md

@@ -215,3 +215,83 @@ pig install age -v 14;   # install for PG 14
 ```sql
 CREATE EXTENSION age;
 ```
+
+
+
+
+## Usage
+
+> [age: AGE graph database extension](https://github.com/apache/age)
+
+Apache AGE brings graph database capabilities to PostgreSQL using the openCypher query language. It enables hybrid querying that combines SQL and Cypher, property indexes on vertices and edges, and the ability to query multiple graphs.
+
+Each session requires loading the extension:
+
+```sql
+CREATE EXTENSION age;
+LOAD 'age';
+SET search_path = ag_catalog, "$user", public;
+```
+
+### Graph Operations
+
+Create a graph:
+
+```sql
+SELECT create_graph('my_graph');
+```
+
+Create vertices:
+
+```sql
+SELECT * FROM cypher('my_graph', $$
+    CREATE (:Person {name: 'Alice', age: 30})
+$$) AS (v agtype);
+
+SELECT * FROM cypher('my_graph', $$
+    CREATE (:Person {name: 'Bob', age: 25})
+$$) AS (v agtype);
+```
+
+Create edges:
+
+```sql
+SELECT * FROM cypher('my_graph', $$
+    MATCH (a:Person), (b:Person)
+    WHERE a.name = 'Alice' AND b.name = 'Bob'
+    CREATE (a)-[e:KNOWS {since: 2020}]->(b)
+    RETURN e
+$$) AS (e agtype);
+```
+
+Query the graph:
+
+```sql
+SELECT * FROM cypher('my_graph', $$
+    MATCH (v)-[r]-(v2)
+    RETURN v, r, v2
+$$) AS (v agtype, r agtype, v2 agtype);
+```
+
+### Cypher Query Features
+
+AGE supports standard Cypher clauses including `MATCH`, `CREATE`, `SET`, `DELETE`, `RETURN`, `WITH`, `WHERE`, `ORDER BY`, `SKIP`, and `LIMIT`. Data is stored using the `agtype` data type, which extends JSON with graph-specific types for vertices, edges, and paths.
+
+Pattern matching with variable-length paths:
+
+```sql
+SELECT * FROM cypher('my_graph', $$
+    MATCH (a:Person)-[:KNOWS*1..3]->(b:Person)
+    RETURN a.name, b.name
+$$) AS (source agtype, target agtype);
+```
+
+Hybrid SQL/Cypher queries allow joining graph results with relational tables:
+
+```sql
+SELECT t.*, c.* FROM my_table t
+JOIN cypher('my_graph', $$
+    MATCH (n:Person) RETURN n.name, id(n)
+$$) AS c(name agtype, id agtype)
+ON t.graph_id = c.id;
+```