Bug reference: 18482 Logged by: yincai.jiang Email address: 13080839167@163.com PostgreSQL version: 15.4 Operating system: red hat Description:
version:PostgreSQL 15.4 on aarch64-unknown-linux-gnu, compiled by gcc (GCC) 7.3.1 20180712 (Red Hat 7.3.1-6), 64-bit
The first data obtained through the following query SELECT "id","customname","customcodesap","operationreason","status","rebateprogress","rebateorder","createtime","updatetime","createuserid","createusername","updateuserid","updateusername","isdelete" FROM "fds_custom" ORDER BY "rebateorder";
It does not match the first piece of data obtained after the following execution. SELECT "id","customname","customcodesap","operationreason","status","rebateprogress","rebateorder","createtime","updatetime","createuserid","createusername","updateuserid","updateusername","isdelete" FROM "fds_custom" ORDER BY "rebateorder" LIMIT 10 offset 0;
I think you need to demonstrate the bug with actual data so people can reproduce it. More likely rebateorder is insufficient for a deterministic ordering of the result set.
