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.

Postgres doesn't use the primary key for on disk ordering. MySQL does.

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?