postgres is a bad datawarehouse - column size limitations #36453
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
octavia-squidington-iii
added
the
area/documentation
evantahler
changed the title
gisripa
approved these changes
Mar 25, 2024
jbfbell
suggested changes
Mar 25, 2024
| Postgres, while an excellent relational database, is not a data warehouse. | ||
|
|
||
| 1. Postgres is likely to perform poorly with large data volumes. Even postgres-compatible destinations (e.g. AWS Aurora) are not immune to slowdowns when dealing with large writes or updates over ~500GB. Especially when using normalization with `destination-postgres`, be sure to monitor your database's memory and CPU usage during your syncs. It is possible for your destination to 'lock up', and incur high usage costs with large sync volumes. | ||
| 2. Postgres column size limitations are likley to cause colisions when used as a destination reciving data from highly-nested and flattened sources. |
There was a problem hiding this comment.
Suggested change
| 2. Postgres column size limitations are likley to cause colisions when used as a destination reciving data from highly-nested and flattened sources. | |
| 2. Postgres column [name length limitations](https://www.postgresql.org/docs/current/limits.html) are likely to cause collisions when used as a destination receiving data from highly-nested and flattened sources, e.g. `{63 byte name}_a` and `{63 byte name}_b` will both be truncated to `{63 byte name}` which causes postgres to throw an error that a duplicate column name was specified. |
There was a problem hiding this comment.
Added a little context feel free to reword
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.