Hi Khushboo, I tested again this morning to collect details, and it's working fine !!?? whereas I spent 1-2 hour the 6 nov with this precision pb, before to test on pgsql... sorry :( it's may be linked to the "big" Windows update of last week partially completed before I restart my computer a 2nd time this WE.
Windows 10 Pro Firefox 82.0.2 64Bits PostgreSQL 12.4 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39), 64-bit Thanks, Alain On Mon, Nov 9, 2020 at 3:44 AM Khushboo Vashi < khushboo.va...@enterprisedb.com> wrote: > Hi, > > I can not reproduce this issue at my end with pgAdmin v4.27. > Please provide OS, Browser and PG details. > > Thanks, > Khushboo > > On Fri, Nov 6, 2020 at 3:19 PM Alain Dupeyron <adupey...@yahoo.fr> wrote: > >> Hello, >> >> In PgAdmin 4.27 bigint values are not displayed correctly, >> The 2-3 last finest digits are to 000 >> example here 6000 insteaf of 6033 ?? >> >> >> select '2807160139143706033', 2807160139143706033, >> x'26f50946094bf5b1'::bigint, x'26f50946094bf5b1'::bit(64) >> >> '?column?' '?column?' 'int8' 'bit' >> 2807160139143706033 2807160139143706000 2807160139143706000 >> 0010011011110101000010010100011000001001010010111111010110110001 >> >> >> expected result from psql : >> >> ?column? | ?column? | int8 >> | bit >> >> ---------------------+---------------------+---------------------+------------------------------------------------------------------ >> 2807160139143706033 | 2807160139143706033 | 2807160139143706033 | >> 0010011011110101000010010100011000001001010010111111010110110001 >> (1 ligne) >> >> bug/display problem ? >> >> Thanks >> >
