Re: BUG #18482: The first data after paging is inconsistent with the actual first data

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: BUG #18482: The first data after paging is inconsistent with the actual first data
Дата
Msg-id CAKFQuwaw3kD0NSz6EkbTPA3s=e6j7h=0dsDdf_-q77XrrOk4mw@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #18482: The first data after paging is inconsistent with the actual first data  (PG Bug reporting form <noreply@postgresql.org>)
Список pgsql-bugs
On Tue, May 28, 2024, 10:40 PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

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.

David J.


В списке pgsql-bugs по дате отправления:

Предыдущее
От: Japin Li
Дата:
Сообщение: Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
Следующее
От: "Haifang Wang (Centific Technologies Inc)"
Дата:
Сообщение: RE: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607