[pull] master from cube-js:master #66
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
) Right now, we use both flags: used and touch. We already had LRU cache for a long time with the touch flag to reduce the number of updates in the Cache Store, but we didn't do it for the used. This leads to a situation where, for a schema with 100 pre-aggs, we will do 200 cache sets per 1 minute because the default refresh interval is set to 30 seconds.
List of changes: - Parse explicit `DISTINCT` option with set operators (e.g. `UNION DISTINCT`) - `array_agg` function can now be prefixed with `pg_catalog.` - New introspection tables are supported: - `pg_auth_members` - `pg_available_extension_versions` - `pg_cast` - `pg_event_trigger` - `pg_foreign_data_wrapper` - `pg_foreign_server` - `pg_foreign_table` - `pg_language` - `pg_locks` - `pg_operator` - `pg_rewrite` - `pg_tablespace` - `pg_timezone_abbrevs` - `pg_timezone_names` - `pg_user_mapping` - New introspection functions are supported: - `pg_is_in_recovery` - `pg_postmaster_start_time` - `pg_tablespace_location` - `txid_current` - System field `xmin` added to the following introspection tables: - `pg_am` - `pg_attribute` - `pg_class` - `pg_constraint` - `pg_description` - `pg_extension` - `pg_index` - `pg_namespace` - `pg_proc` - `pg_type` - `pg_namespace`'s `nspacl` field now has correct type (`List(Utf8)`) - `AGE` function now accepts values of type `xid` - `"char"` casts are being replaced with `text` casts - `xid` casts are being replaced with `unsigned int` casts - New `PgType`s added: - `[ARRAY]PGAM` - `[ARRAY]PGCAST` - `[ARRAY]PGEVENTTRIGGER` - `[ARRAY]PGEXTENSION` - `[ARRAY]PGFOREIGNDATAWRAPPER` - `[ARRAY]PGFOREIGNSERVER` - `[ARRAY]PGLANGUAGE` - `CTID` system field is replaced with `NULL` in data queries Signed-off-by: Alex Qyoun-ae <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.3)
Can you help keep this open source service alive? 💖 Please sponsor : )