Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Mixture of Materialized Views / Tables In concepts #254
Comments
|
I don't think this difference is intentional, so switching to a materialized view makes sense for consistency. Tables and materialized views are pretty similar in Postgres...the main difference is that the query used to create a materialized view is retained, so the view can be regenerated with Materialized views apparently don't support "automatic generation of OIDs", which are object identifiers assigned to rows. These are turned off by default for user generated tables anyway, so this doesn't seem to matter. |
tompollard
added a commit
that referenced
this issue
Jul 10, 2017
|
|
tompollard |
8961619
|
|
Yeah little bit of inconsistency that's best fixed! Thanks @tompollard ! |
alistairewj
closed this
Jul 11, 2017
tompollard
added a commit
that referenced
this issue
Jul 11, 2017
|
|
tompollard |
50cc75a
|
jraffa commentedJul 10, 2017
In at least two of the concepts:
crrtdurationsandventdurationsthe end result is a table, while the others produce materialized views. Just wondering if this is intended behaviour, or the result of some legacy code.