pg_ivm/Makefile

# contrib/pg_ivm/Makefile

MODULE_big = pg_ivm
OBJS = \
	$(WIN32RES) \
	createas.o \
	matview.o \
	pg_ivm.o \
	ruleutils.o \
	subselect.o
PGFILEDESC = "pg_ivm - incremental view maintenance on PostgreSQL"

EXTENSION = pg_ivm
DATA = pg_ivm--1.0.sql \
       pg_ivm--1.0--1.1.sql pg_ivm--1.1--1.2.sql pg_ivm--1.2--1.3.sql \
       pg_ivm--1.3--1.4.sql pg_ivm--1.4--1.5.sql pg_ivm--1.5--1.6.sql \
       pg_ivm--1.6--1.7.sql

REGRESS = pg_ivm create_immv refresh_immv

PG_CONFIG ?= pg_config
PGXS := $(shell $(PG_CONFIG) --pgxs)
include $(PGXS)
Initial release of pg_ivm 1.0 2022-03-31 12:48:53 +00:00			`# contrib/pg_ivm/Makefile`

Split files to make it easier to follow the core code 2022-04-27 05:45:47 +00:00			`MODULE_big = pg_ivm`
			`OBJS = \`
			`$(WIN32RES) \`
			`createas.o \`
			`matview.o \`
Support min/max aggregates (#18) In order to re-calculate min/max values for groups where the min or max value is deleted, we need the view query definition in string form. However, pg_get_viewdef cannot be used for this purpose because IMMV's defenition is in pg_ivm_immv but not pg_rewrite. Therefore, we have to convert query definition in pg_ivm_immv to query definition string. We can use pg_get_querydef in PG15, but we cannot in PG14 or earlier, so we use codes in ruleutil.c copied from PG13 or PG14 depending versions. 2022-07-25 04:11:33 +00:00			`pg_ivm.o \`
Add CTE support (#47) Simple CTEs which does not contain aggregates or DISTINCT are now supported similarly to simple sub-queries. Before a view is maintained, all CTEs are converted to corresponding subqueries to enable to treat CTEs as same as subqueries. For this end, codes of the static function inline_cte in the core (optimizer/plan/subselect.c) was imported. Prohibit Unreferenced CTE is prohibited. When a table in a unreferenced CTE is TRUNCATEd, the contents of the IMMV is not affected so it must not be truncated. For confirming it at the maintenance time, we have to check if the modified table used in a CTE is actually referenced. Although it would possible, we just disallow to create such IMMVs for now since such unreferenced CTE is useless unless it doesn't contain modifying commands, that is already prohibited. 2023-01-30 02:28:27 +00:00			`ruleutils.o \`
			`subselect.o`
Split files to make it easier to follow the core code 2022-04-27 05:45:47 +00:00			`PGFILEDESC = "pg_ivm - incremental view maintenance on PostgreSQL"`

Initial release of pg_ivm 1.0 2022-03-31 12:48:53 +00:00			`EXTENSION = pg_ivm`
Fix Makefile to install pg_ivm--1.3--1.4.sql (#45) This should have be included in the previous commit but was accidentally forgotten. Issue #43 2023-01-10 09:41:50 +00:00			`DATA = pg_ivm--1.0.sql \`
			`pg_ivm--1.0--1.1.sql pg_ivm--1.1--1.2.sql pg_ivm--1.2--1.3.sql \`
Prepare 1.7 2023-09-13 02:13:40 +00:00			`pg_ivm--1.3--1.4.sql pg_ivm--1.4--1.5.sql pg_ivm--1.5--1.6.sql \`
			`pg_ivm--1.6--1.7.sql`
Initial release of pg_ivm 1.0 2022-03-31 12:48:53 +00:00
Add refresh_immv() function refresh_immv(immv_name, with_data) is a function to refresh IMMV like REFRESH MATERIALIZED VIEW command. It has two argument. immv_name is incrementally maintainable materialized view's name, and with_data is an option that is corresponding to the WITH [NO] DATA option. When with_data is set false, the IMMV gets unpopulated. One of differences between IMMVs unpopulated by this function and normal materialized views unpopulated by REFRESH ... WITH NO DATA is that such IMMVs can be referenced by SELECT but return no rows, while unpopulated materialized views are not scanable. The behaviour may be changed in future to raise an error when unpopulated an IMMV is scanned. 2022-06-13 09:22:28 +00:00			`REGRESS = pg_ivm create_immv refresh_immv`
Initial release of pg_ivm 1.0 2022-03-31 12:48:53 +00:00
Allow to variable PG_CONFIG together with make command 2022-11-25 09:33:27 +00:00			`PG_CONFIG ?= pg_config`
Initial release of pg_ivm 1.0 2022-03-31 12:48:53 +00:00			`PGXS := $(shell $(PG_CONFIG) --pgxs)`
			`include $(PGXS)`