Re: Bug report - incorrect value displayed in jsonb column for large numbers - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Bug report - incorrect value displayed in jsonb column for large numbers
Date
Msg-id 19115.1554310090@sss.pgh.pa.us
Whole thread Raw
In response to Bug report - incorrect value displayed in jsonb column for large numbers  (Michał Iwańczuk <miwanczuk7@gmail.com>)
Responses Re: Bug report - incorrect value displayed in jsonb column for largenumbers  (Jerry Sievert <jerry@legitimatesounding.com>)
List pgsql-bugs
=?UTF-8?B?TWljaGHFgiBJd2HFhGN6dWs=?= <miwanczuk7@gmail.com> writes:
> 1) create table:

> CREATE TABLE document_wrapper(
>     id integer NOT NULL,
>     document jsonb NOT NULL,
>     CONSTRAINT document_pkey PRIMARY KEY (id))WITH (
>     OIDS = FALSE)
> TABLESPACE pg_default;

> 2) insert value

> insert into document_wrapper(id, document) values(-8,
> '{"id":101861191707868275}');

> 3) select value

> SELECT document FROM document_wrapper where id = -8;

> 4) Observe incorrect result (note 0 at the end):
> { "id": 101861191707868270 }?


Works fine for me in psql, so whatever the problem is here, it's
not in the Postgres server.  You should try asking in the pgadmin
lists, instead.  (I'm rather surprised to hear that pgadmin does
anything special with jsonb values, but apparently it does ...)

            regards, tom lane



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15732: Jessie backports removed from network
Next
From: Tom Lane
Date:
Subject: Re: BUG #15383: Join Filter cost estimation problem in 10.5