News for hackers. Stuff that matters.
Re:How to Get the Most Out of Postgres Memory Settings by sgarland on Thursday June 13, 2024 @07:36AM (#40668343)
> same clustering problem

Not necessarily. Depending on your secrecy desire, you could include the internal ID in JWT or cookie, and then locate the row (including the external UUID) using that. Another option would be to build an index with `INCLUDE external_id`. That way, it doesn’t impact the B+tree (kind of) but it still gets pulled along for query results. The leaf nodes would become larger, but the overall ordering wouldn’t change (I think – never actually tried this).

Re:How to Get the Most Out of Postgres Memory Settings by hot_gril on Thursday June 13, 2024 @12:07PM (#40671399)
If you mean to encrypt your internal IDs when sending to clients and decrypt when receiving, it'd work. I've never seen it done this way, maybe because with standard 2048-bit RSA you get a 2048-bit output at least, which would bloat up the API responses.