I have now VERY strong argument to consider it is as a bug: if there a understandable for SQL language sequence which sorts in other fashion when adding "LIMIT".
I did try the same with a last name starting with "G" (there also more than one entry with identical surnames) and it worked ok(the results were represented as I waited). this one last example brings me to conseder it is as a bug. id | str_last_name -----+---------------------- 83 | GXXXXXXXXX 175 | GXXXXXXXXX and id | str_last_name ----+---------------------- 83 | GXXXXXXXXX (1 строка) select id, str_last_name from tbl_owners_individual order by str_last_name offset 26; and select id, str_last_name from tbl_owners_individual order by str_last_name offset 26 limit 1; corresponding... and even sorting by id: select id, str_last_name from tbl_owners_individual where id in (83,175,111,1) order by str_last_name; id | str_last_name -----+---------------------- 83 | GXXXXXXXXX 175 | GXXXXXXXXX 1 | Kolesnik 111 | Kolesnik (4 строки) select id, str_last_name from tbl_owners_individual where id in (83,175,111,1) order by id; id | str_last_name -----+---------------------- 1 | Kolesnik 83 | GXXXXXXXXX 111 | Kolesnik 175 | GXXXXXXXXX (4 строки) anyway sorted by id results the record with the "1" id appear before the record with the id "111". -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
