On Sunday, October 25th, 2026 at 12:52 PM, Hannu Krosing <[email protected]> wrote:
> Hi Greg > > Please take a look at a generalized design for the compression dictionary > > In email: [PATCH v1] Generic Datum Encoding and Compression Contexts > (pg_encoding_type, pg_encoding_context) Hey Hannu, Sure thing, I'll give that a look and see how the two designs might become one. > I have used this myself in dictionary compression for zstd and lz4 and > for keeping Apache Avro schemas for JSON and JSONB encodings and > defining cascaded Avro+zstd Interesting use cases. > And also I used the same for storing quantization tables for pgvector > int8 and other quantizations Hmmm... ok. > This could also be used for other "encoding" tasks, like having a > public key for writes and a more restricted private key for reads, > etc. Are we at risk of over-generalizing/loading this one idea too much? I'd imagine you to say "no", but I had to ask. :) > The main point is that having a generic facility for these kinds of > tasks would benefit many use cases. I'm all for reuse and a generic facility if one can be agreed upon. > Cheers, > Hannu best. -greg
