pg_ivm | IVM (Incremental View Maintenance) implementation as a PostgreSQL extension | Application Framework library

by sraoss C Version: v1.5.1 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | pg_ivm Summary

pg_ivm is a C library typically used in Server, Application Framework applications. pg_ivm has no bugs, it has no vulnerabilities and it has low support. However pg_ivm has a Non-SPDX License. You can download it from GitHub.

Incremental View Maintenance (IVM) is a way to make materialized views up-to-date in which only incremental changes are computed and applied on views rather than recomputing the contents from scratch as REFRESH MATERIALIZED VIEW does. IVM can update materialized views more efficiently than recomputation when only small parts of the view are changed. There are two approaches with regard to timing of view maintenance: immediate and deferred. In immediate maintenance, views are updated in the same transaction that its base table is modified. In deferred maintenance, views are updated after the transaction is committed, for example, when the view is accessed, as a response to user command like REFRESH MATERIALIZED VIEW, or periodically in background, and so on. pg_ivm provides a kind of immediate maintenance, in which materialized views are updated immediately in AFTER triggers when a base table is modified.

Support

Quality

Security

License

Reuse

Support

pg_ivm has a low active ecosystem.

It has 461 star(s) with 15 fork(s). There are 16 watchers for this library.

It had no major release in the last 12 months.

There are 11 open issues and 11 have been closed. On average issues are closed in 26 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of pg_ivm is v1.5.1

Quality

pg_ivm has no bugs reported.

Security

pg_ivm has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

pg_ivm has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

pg_ivm releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of pg_ivm

Get all kandi verified functions for this library.

pg_ivm Key Features

No Key Features are available at this moment for pg_ivm.

pg_ivm Examples and Code Snippets

No Code Snippets are available at this moment for pg_ivm.

Community Discussions

Trending Discussions on Application Framework

What is meant by required-api: param name=”#target” in config.xml file of AGL widgets?

QUESTION

What is meant by required-api: param name=”#target” in config.xml file of AGL widgets?

Asked 2020-Mar-06 at 09:53

I am trying to understand various available AGL specific options that we can give in config.xml and I am referring to the link below

https://docs.automotivelinux.org/docs/en/halibut/apis_services/reference/af-main/2.2-config.xml.html

This is the sample config.xml file

...

ANSWER

Answered 2020-Mar-06 at 09:48

I figured out why we need this

required-api: param name="#target"

OPTIONAL(not compulsory)

It declares the name of the unit(in question it is main) requiring the listed apis. Only one instance of the param “#target” is allowed. When there is not instance of this param, it behave as if the target main was specified.

Source https://stackoverflow.com/questions/60561230

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install pg_ivm

To install pg_ivm, execute this in the module's directory:. If you installed PostgreSQL from rpm or deb, you will need the devel package (for example, postgresql14-devel or postgresql-server-dev-14).

Support

Currently, IMMV's view definition can contain inner joins, DISTINCT clause, some built-in aggregate functions, simple sub-queries in FROM clause, and simple CTE (WITH query). Inner joins including self-join are supported, but outer joins are not supported. Supported aggregate functions are count, sum, avg, min and max. Other aggregates, sub-queries which contain an aggregate or DISTINCT clause, sub-queries in other than FROM clause, window functions, HAVING, ORDER BY, LIMIT/OFFSET, UNION/INTERSECT/EXCEPT, DISTINCT ON, TABLESAMPLE, VALUES, and FOR UPDATE/SHARE can not be used in view definition. The base tables must be simple tables. Views, materialized views, inheritance parent tables, partitioned tables, partitions, and foreign tables can not be used. The targetlist cannot contain system columns, columns whose name starts with __ivm_. Logical replication is not supported, that is, even when a base table at a publisher node is modified, IMMVs at subscriber nodes defined on these base tables are not updated.

Find more information at: