pg_fetch_cycle is an experimental PostgreSQL extension built on top of pg_net that orchestrates multi-step HTTP request sequences. It enables things like paginated API scraping, request chaining, and stateful HTTP workflows.
2e4bca8065
additionally I improved the options functionality and added a cycle debug option where steps are not deleted automatically. |
||
|---|---|---|
| DIAGRAM.md | ||
| install.sh | ||
| LICENSE | ||
| PATTERN_RELOAD.md | ||
| pg_fetch_cycle--1.0--noop.sql | ||
| pg_fetch_cycle--1.0.sql | ||
| pg_fetch_cycle--noop--1.0.sql | ||
| pg_fetch_cycle.control | ||
| README.md | ||
| SUMMARY.md | ||
pg_fetch_cycle PostgreSQL Extension
A PostgreSQL extension for managing fetch cycles with pg_net.
Documentation
- SUMMARY.md - Overview of what this extension does
- DIAGRAM.md - System architecture diagram
- PATTERN_RELOAD.md - Hot-reload development pattern using "noop" versions
Dependencies
pg_net: PostgreSQL HTTP client extensioncitext: Case-insensitive text type extension
Installation
-
Install the extension files to your PostgreSQL extensions directory:
# Development mode - create symbolic links for easy reloading ./install.sh -
Install the pg_fetch_cycle extension (dependencies will be installed automatically):
create extension pg_fetch_cycle version 'noop'; select pg_fetch_cycle_reload();
Development
Reloading During Development
To reload the extension during development:
-
For reloading procedures and functions:
select pg_fetch_cycle_reload(); -
For completely dropping and recreating the extension:
select pg_fetch_cycle_recreate();