Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for materialized views #40

dcherk opened this issue Dec 12, 2017 · 1 comment


Copy link

commented Dec 12, 2017

Expected behavior

For PostgreSQL: Materialized views should show up in either the table tree or the view tree. They should also participate in auto-complete.

Please see:

Current behavior

PostgreSQL's materialized views are not shown in any tree. They do not participate in auto-complete.


This comment has been minimized.

Copy link

commented Dec 12, 2017

Did some research.

As per

The information schema consists of a set of views that contain information about the objects defined in the current database. The information schema is defined in the SQL standard and can therefore be expected to be portable and remain stable — unlike the system catalogs, which are specific to PostgreSQL and are modeled after implementation concerns. The information schema views do not, however, contain information about PostgreSQL-specific features; to inquire about those you need to query the system catalogs or other PostgreSQL-specific views.

Because materialized views are a PostgreSQL extension (, this feature would be hard to implement, as HeidiSQL would need to know PostgreSQL-specific details.

Nonetheless, this would be a very useful feature to have, as materialized views have common real-world uses.


@ansgarbecker ansgarbecker changed the title Add support for PostgreSQL's materialized views Add support for materialized views Dec 12, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.