Thread: BUG #17766: Issue in asc, limit and offset for pagination.
The following bug has been logged on the website: Bug reference: 17766 Logged by: PR Gopi krishnan Email address: prgopikrishnan85@gmail.com PostgreSQL version: 15.1 Operating system: windows and linux Description: While getting the rows with the columns called name which has duplicate names, now ascending the rows by name with limit 25 and offset 0,25,50 like this on each query. But the rows are duplicating with the names
On Wed, Feb 1, 2023 at 3:54 PM PG Bug reporting form <noreply@postgresql.org> wrote:
> While getting the rows with the columns called name which has duplicate
> names, now ascending the rows by name with limit 25 and offset 0,25,50 like
> this on each query. But the rows are duplicating with the names
Hi,
> names, now ascending the rows by name with limit 25 and offset 0,25,50 like
> this on each query. But the rows are duplicating with the names
Hi,
You mentioned that the field has duplicate name values, so selecting that column will produce a result set that has duplicates also. A "limit" clause is not going to change that.
If you still think something is not behaving as expected, please provide a reproducible test case.
--
John Naylor
EDB: http://www.enterprisedb.com
--
John Naylor
EDB: http://www.enterprisedb.com
On Wed, Feb 01, 2023 at 06:38:47AM +0000, PG Bug reporting form wrote: > The following bug has been logged on the website: > > Bug reference: 17766 > Logged by: PR Gopi krishnan > Email address: prgopikrishnan85@gmail.com > PostgreSQL version: 15.1 > Operating system: windows and linux > Description: > > While getting the rows with the columns called name which has duplicate > names, now ascending the rows by name with limit 25 and offset 0,25,50 like > this on each query. But the rows are duplicating with the names This is not a bug. Simply make sure that your order by clause is over unique combination. So, if your name has duplicates, then add primary key to order by clause: order by name, id depesz