Hi there, I need to optimise for storage on my tar...
# contributing
c
Hi there, I need to optimise for storage on my target-postgres. Current implementation is optimized to not loose any data, which is nice but isn't convenient for my use case. Example: Some of my text fields would benefit from a pg domain/type and some other text data would be more efficiently stored as bytea. Even better if I could manipulate the tablespace of the schema/table or set a table to be an hydra columnar table, a timescaledb table, or set pg_partman config somehow. I see multiple proposals in GitHub but idk if there is a consensus on a target implementation to force a column type to be something else or to hook into table dll. If there's no consensus I'll just fork target-postgres and do my own thing but just wanted to ask in case that could be contributed back somehow
Given my quick research, it looks like it make sense for this target to be supporting hex data and enum types. So I'll be doing a pull request to support
"contentEncoding":"base16"
+ using sqlalchemy
Enum
, both behind 2 opt-in feature flags to avoid breaking changes
e
Thanks @Clément! I've left some comments in https://github.com/MeltanoLabs/target-postgres/pull/287.
❣️ 1
c
Thank you sir! Really appreciate your support and reactivity 🙏
np 1
😁 1
c
Alright, should be fixed, not sure about the naming of the option so added a bunch of documentation
c
okaaay, let's do something similar for the enum thing
👍 1
c
oof this is way more complex than anticipated
c
Still working on it, struggling to make SQL alchemy understand not to drop the type along with the temporary table
c
oooooook, FINALLY something that works https://github.com/MeltanoLabs/target-postgres/pull/292
👀 1
c
hope it's not too bad 🫡
If there is anything wrong with this PR, lmk