Re: possible bug in PG admin

Its an issue at 2000 records  see picture,  it starts to repeat over and over again

On Fri, Mar 16, 2018 at 3:14 PM, Justin <zzzzz.graf@gmail.com> wrote:

I just noticed something after clicking send button....  the dataset should only be 10,000 records,  yet PGAdmin 4 just keeps dumping out records  its showing 40,000 records??  its appears it goes all wrong at 2,000 record set....

On Fri, Mar 16, 2018 at 3:07 PM, Justin <zzzzz.graf@gmail.com> wrote:

not with psql  but check in pgadmin3 the display was correct

try using this select statement

with dataset as (select * from  generate_series(1,10000))
select *,  now()::date + (random()*10)::integer from dataset
order by 2 desc

out of order does not occur until record 2000

On Fri, Mar 16, 2018 at 1:56 PM, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote:

pgAdmin4 don't do any sorting by itself, it just displays what it receives from server.​

Did you cross verify your output with psql?

I'm not able to re-produce the issue (attaching screenshot).

--

Regards,

Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

On Fri, Mar 16, 2018 at 7:40 PM, Justin <zzzzz.graf@gmail.com> wrote:

see attached picture.

PGadmin the displayed data is not staying in desired sort order  (order by date desc)  per the SQL command ....

The return set is around 4000 rows long,  the  two source tables are 14,000 and 251,340 rows

SQL command
select comment_id , item_id, item_number, item_descrip1, comment_text, comment_date, comment_user 
from item, comment
where item_id = comment_source_id and comment_source = 'I'
and item_active  and comment_text::char(10) = 'List Price'
and comment_date>= '2015-01-01'
order by  comment_date desc

Operating System Windows 7 64bit