pg_materialize
pg_materialize is a utility for generating PostgreSQL creation and refresh scripts from a directory containing Materialized View SQL definitions. It uses psqlparse to transform the SQL into parse trees, identifies which Materialized Views have a dependency on other views by generating a DAG, and produces the correct order for constructing and refreshing these views. The source directory is traversed recursively, cross-schema views are handled correctly, and extraneous transaction syntax blocks are filtered out from the final output. The files from each subsequent run are timestamped with the suffix YYYYMMDD-HHMMSS.sql.
Supported Python Versions
Python 2.7
Python 3.3+
Installation
If you have pip on your system, you can simply install or upgrade the Python library:
pip install -U pg_materialize
Alternately, you can download the source distribution from PyPI, unarchive it, and run:
python setup.py install
Note: both of the methods described above install pg_materialize as a system-wide package. You may consider using virtualenv to create isolated Python environments instead.
Usage
Example Command:
pg_materialize -v \
-i ~/Projects/my_project/src \
-o ~/Projects/my_project/output \
-p _mv \
-I invites
Example Output:
Found 97 Scripts in /Users/ali/Projects/my_project/src Identified 169 Materialized Views, Containing 90 View Dependencies Materialized View Dependencies: 'public.users_mv': ['public.user_addresses_mv', 'public.user_invites_mv'], 'public.orders_mv': ['public.payment_methods_mv'] Selecting 97 Materialized Views for Refresh Successfully Saved Creation Script to ~/Projects/my_project/output/create-20170824-120626.sql Successfully Saved Refresh Script to ~/Projects/my_project/output/refresh-20170824-120626.sql Process Complete!
Example Creation Script:
BEGIN;
-- ~/Projects/my_project/src/public/user_addresses.sql
CREATE MATERIALIZED VIEW IF NOT EXISTS public.user_addresses_mv AS (
SELECT *
FROM public.user_addresses
WHERE created_at >= CURRENT_DATE - INTERVAL '6 MONTHS'
) WITH DATA;
-- ~/Projects/my_project/src/public/user_invites.sql
CREATE MATERIALIZED VIEW IF NOT EXISTS public.user_invites_mv AS (
SELECT *
FROM public.user_invites
WHERE created_at >= CURRENT_DATE - INTERVAL '6 MONTHS'
) WITH DATA;
-- ~/Projects/my_project/src/public/payment_methods.sql
CREATE MATERIALIZED VIEW IF NOT EXISTS public.payment_methods_mv AS (
SELECT *
FROM public.payment_methods
WHERE created_at >= CURRENT_DATE - INTERVAL '6 MONTHS'
) WITH DATA;
-- ~/Projects/my_project/src/public/users.sql
CREATE MATERIALIZED VIEW IF NOT EXISTS public.users_mv AS (
SELECT *
FROM public.users
WHERE created_at >= CURRENT_DATE - INTERVAL '6 MONTHS'
) WITH DATA;
-- ~/Projects/my_project/src/public/orders.sql
CREATE MATERIALIZED VIEW IF NOT EXISTS public.orders_mv AS (
SELECT *
FROM public.orders
WHERE created_at >= CURRENT_DATE - INTERVAL '6 MONTHS'
) WITH DATA;
COMMIT;
Example Refresh Script:
BEGIN;
REFRESH MATERIALIZED VIEW CONCURRENTLY public.user_addresses_mv;
REFRESH MATERIALIZED VIEW CONCURRENTLY public.payment_methods_mv;
REFRESH MATERIALIZED VIEW CONCURRENTLY public.users_mv;
REFRESH MATERIALIZED VIEW CONCURRENTLY public.orders_mv;
COMMIT;
Options
pg_materialize accepts the following command line arguments.
Analyzes dependencies without actually generating the output files.
The directory for the PostgreSQL scripts to analyze.
Regex pattern to match when ignoring refresh on Materialized Views (i.e. hist for users_mv_hist).
The directory for the output creation and refresh scripts.
Materialized View regex pattern to match (i.e. _mv for users_mv).
Enables verbose logging.
Metadata
Release files for pg-materialize 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pg-materialize-0.4.1.tar.gz | 21.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pg_materialize-0.4.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 29.8 kB
Release files / pg-materialize-0.4.1.tar.gz
| Download URL | pg-materialize-0.4.1.tar.gz |
|---|---|
| Size | 21.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
12b66d859295d6b4be7e50194e026ef10f7232cc4e305c05b9917614d8e63024
|
|
BLAKE2b-256 checksum How to use checksums |
5088986d83cc191b97305144d1fcfe1ffd51aa670a3700f682e07b8b4a510282
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pg_materialize-0.4.1-py2.py3-none-any.whl
| Download URL | pg_materialize-0.4.1-py2.py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
00604462015aec28c753116c1e1b6efa89bb00792bcca17ac24b5326cf753716
|
|
BLAKE2b-256 checksum How to use checksums |
dacd59d4a37cdac27cbe42dc619e5d6408b62b54a2061fea8e0b979b588f84e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pg-materialize 0.4.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.