Do not compress serialized_object data when storing it.
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
This stems from comments in issue #8.
Postgres automatically compresses column data for rows in which it makes sense to do so. Remove the erlang-side compression during serialization/deserialization. This will also simplify use of fields within jsonb columns when we move to jsonb.
Note that this also requires a data migration to covert explicitly compressed data to uncompressed for existing records.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with issue #8 and the Erlang serialization/deserialization paths for serialized_object data; verify how explicitly compressed existing records are represented. Done means new storage leaves compression to PostgreSQL, existing records are converted by a data migration, and the approach remains compatible with the planned jsonb columns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang, postgresql
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100