Timeline for DISTINCT forces re-sorting of data on PostgreSQL
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 21, 2021 at 19:16 | comment | added | StasM | Unfortunately, in this particular scenario stateful client & cursors is not an option. | |
| Jul 21, 2021 at 18:31 | comment | added | jjanes | The efficient way to deal with pagination is to use cursors, with a "stateful" client or app server. | |
| Jul 21, 2021 at 18:20 | history | edited | jjanes | CC BY-SA 4.0 |
added 43 characters in body
|
| Jul 21, 2021 at 17:12 | comment | added | StasM | That's disappointing that Postgres doesn't do this obvious optimization. But I guess that answers my question, thanks! Any ideas if there's another way to achieve the same? Limiting the work set size is pretty common for pagination... | |
| Jul 21, 2021 at 14:58 | history | answered | jjanes | CC BY-SA 4.0 |