-
-
Notifications
You must be signed in to change notification settings - Fork 181
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
Documentation: PgSync with Postgres Materialized Views #175
Comments
Materialized views are not yet supported. |
I enthusiastically support this enhancement. We're retooling an application funded by NIH that aggregates 10+ large data sources that we stage into Postgres as raw XML and JSON and then use materialized views to unroll the structures. We're currently indexing using the bare Lucene APIs, and PgSync offers us a perfect means to cleanly transition to ElasticSearch. If I can avoid having to stage the materialized views into actual tables, we've a perfect solution. |
Will revisit this shortly. |
Hello, I read that materialized view are not supported, is that changed? Thank you |
This is currently in progress. Will keep you updated. |
Support for views is now detailed here |
Can we have additional documentation on how pgsync works with Postgres Materialized Views? Should the name of the view be the 'table' name in the schema? When the view is concurrently refreshed, does pgsync only sync the changes in the view with elastic-search (like it does with tables), or re-add every entry in the view? I'd really recommend some clarification on how views would work with pgsync. Thanks!
The text was updated successfully, but these errors were encountered: