12 ms·

> hacking on a separate unique UUID for public use is also bad. Is it bad just because of the extra bytes used, or something else?

• deleted 3y ago
  [deleted]
• arghwhat 3y ago
  You need to maintain a UNIQUE index and have two IDs, with the one set as primary key solely existing for on-disk ordering. It's a nasty hack.
  • wiredfool 3y ago
    Postgres doesn't use the primary key for on disk ordering. MySQL does.
    • arghwhat 3y ago
      Ah, good point. The concern about on-disk ordering then only applies to other databases. I suppose the index order may still be relevant for PostgreSQL?