Re: Bug report - incorrect value displayed in jsonb column for large numbers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michał Iwańczuk <miwanczuk7(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Bug report - incorrect value displayed in jsonb column for large numbers
Date: 2019-04-03 16:48:10
Message-ID: 19115.1554310090@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?UTF-8?B?TWljaGHFgiBJd2HFhGN6dWs=?= <miwanczuk7(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-04-03 17:07:41 Re: BUG #15383: Join Filter cost estimation problem in 10.5
Previous Message PG Bug reporting form 2019-04-03 15:29:18 BUG #15732: Jessie backports removed from network