mirror of
https://github.com/nickpoida/og-aws.git
synced 2025-02-13 10:21:57 +00:00
Made changes requested for pr
This commit is contained in:
parent
12f149dfde
commit
7d6c2d5558
1 changed files with 2 additions and 2 deletions
|
@ -1252,8 +1252,8 @@ Redshift
|
||||||
- ❗ Never resize a live cluster. The resize operation takes hours depending on the dataset size. In rare cases, the operation may also get stuck and you'll end up having a non-functional cluster. The safer approach is to create a new cluster from a snapshot, resize the new cluster and shut down the old one.
|
- ❗ Never resize a live cluster. The resize operation takes hours depending on the dataset size. In rare cases, the operation may also get stuck and you'll end up having a non-functional cluster. The safer approach is to create a new cluster from a snapshot, resize the new cluster and shut down the old one.
|
||||||
- Redshift has reserved keywords which are not present in Postgres (see full list [here](https://docs.aws.amazon.com/redshift/latest/dg/r_pg_keywords.html)). Watch out for DELTA ([Delta Encodings](https://docs.aws.amazon.com/redshift/latest/dg/c_Delta_encoding.html)).
|
- Redshift has reserved keywords which are not present in Postgres (see full list [here](https://docs.aws.amazon.com/redshift/latest/dg/r_pg_keywords.html)). Watch out for DELTA ([Delta Encodings](https://docs.aws.amazon.com/redshift/latest/dg/c_Delta_encoding.html)).
|
||||||
- Redshift does not support many Postgres functions, most notably several date/time-related and aggregation functions. See the [full list here](https://docs.aws.amazon.com/redshift/latest/dg/c_unsupported-postgresql-functions.html).
|
- Redshift does not support many Postgres functions, most notably several date/time-related and aggregation functions. See the [full list here](https://docs.aws.amazon.com/redshift/latest/dg/c_unsupported-postgresql-functions.html).
|
||||||
- 🔹 [Choosing Sort Key](http://docs.aws.amazon.com/redshift/latest/dg/t_Sorting_data.html) is very important since you can not change sort key after table created. If you need to change sort key or distribution key of a table, you need to create a new table with new key and move your data into it with a query like "insert into new_table select * from old_table".
|
- 🔹 [Choosing a sort key](http://docs.aws.amazon.com/redshift/latest/dg/t_Sorting_data.html) is very important since you can not change a table‘s sort key after it is created. If you need to change the sort or distribution key of a table, you need to create a new table with the new key and move your data into it with a query like “insert into new_table select * from old_table“.
|
||||||
- ❗🚪 When moving data with a query that looks like “insert into x select from y;” you need to have as twice as much space as table “y” takes up available on your cluster's disk. Redshift first copies the data to disk and then to the new table. A good [article](https://www.periscopedata.com/blog/changing-dist-and-sort-keys-in-redshift.html) about how to this for big tables.
|
- ❗🚪 When moving data with a query that looks like “insert into x select from y“ you need to have as twice as much space as table “y“ takes up available on your cluster‘s disk. Redshift first copies the data to disk and then to the new table. [Here](https://www.periscopedata.com/blog/changing-dist-and-sort-keys-in-redshift.html) is a good article on how to this for big tables.
|
||||||
|
|
||||||
EMR
|
EMR
|
||||||
---
|
---
|
||||||
|
|
Loading…
Reference in a new issue