pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #18482: The first data after paging is inconsistent with the actual first data
2+ messages / 2 participants
[nested] [flat]

* BUG #18482: The first data after paging is inconsistent with the actual first data
@ 2024-05-28 03:01 PG Bug reporting form <noreply@postgresql.org>
  2024-05-28 17:21 ` Re: BUG #18482: The first data after paging is inconsistent with the actual first data David G. Johnston <david.g.johnston@gmail.com>
  0 siblings, 1 reply; 2+ messages in thread

From: PG Bug reporting form @ 2024-05-28 03:01 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org; +Cc: 13080839167@163.com

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;



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: BUG #18482: The first data after paging is inconsistent with the actual first data
  2024-05-28 03:01 BUG #18482: The first data after paging is inconsistent with the actual first data PG Bug reporting form <noreply@postgresql.org>
@ 2024-05-28 17:21 ` David G. Johnston <david.g.johnston@gmail.com>
  0 siblings, 0 replies; 2+ messages in thread

From: David G. Johnston @ 2024-05-28 17:21 UTC (permalink / raw)
  To: 13080839167@163.com, PostgreSQL Bug List <pgsql-bugs@lists.postgresql.org>

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.

^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2024-05-28 17:21 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-05-28 03:01 BUG #18482: The first data after paging is inconsistent with the actual first data PG Bug reporting form <noreply@postgresql.org>
2024-05-28 17:21 ` David G. Johnston <david.g.johnston@gmail.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox