On Thu, Oct 24, 2019 at 3:35 AM Laiszner Tamás <t.laiszner@xxxxxxxxxxx> wrote:
Actually, this is not such a unique idea: https://instagram-engineering.com/sharding-ids-at-instagram-1cf5a71e5a5c
Thanks for the suggestion to split up the primary key into components. But even going down this way, packing the components into one superstructure (composite type) would be beneficial as the same scheme is used across multiple tables. And we are back at the original problem.
This is probably a completely naive question, but why not store this in a text field?
