While I think you’re correct that the GUI should have this options, I am of the opinion that you should look at the design of your specific screen. When a user has to dig trough dozens of pages there is something wrong with the useability of this screen. (opinion)
I’m sure these records are related to something for example a specific customer or product. Let the user first select the correct parent record and zoom into that detailed data afterwards.
Another option would perhaps be to let the users search or ask questions about this data via a connection with a large language model (AI). This way it might be easier to find the data the user needs in order to do their work.
I am curious what a possible use case for this is. I can think of situations where filtering isn’t really possible to limit the results, but I can’t think of a situation that the user wants to jump to a specific page without going through them all.
If something like this gets implemented, please be careful with taking up more space, or make it optional. In my opinion the pagination already takes up too much space, specially on mobile.
I would even encourage to look for alternatives for the whole pagination.
The use case is when a user has limited the data of 100k+ or sometimes a couple of millions in records to the remaining couple of hundreds or as shown in this screenshot to 1.4k.
They need to check several things in the remaining data and they are not always in the exact order you want to work in. Looking at the sorting you could likely see it show up closer to page 10 than the selectable page numbers.