PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID15716
PG Version11.2
OSwindows 10 pro
Opened2019-03-26 15:18:07+00
Reported byJan Magnusson
StatusNew

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      15716
Logged by:          Jan Magnusson
Email address:      (redacted)
PostgreSQL version: 11.2
Operating system:   windows 10 pro
Description:        

The row_to_json() function does not produce any output data, only message.

b.r. Jan
------------------------------------------------------------------------------------
CREATE SCHEMA testing AUTHORIZATION postgres;

CREATE TABLE testing.batch
(
    batch_id integer NOT NULL,
    max_record integer,
    record_count integer,
    creation_ts timestamp without time zone DEFAULT now(),
    CONSTRAINT batch_id_pkey PRIMARY KEY (batch_id)
)
WITH (
    OIDS = FALSE
)
TABLESPACE pg_default;


insert into testing.batch values(1, now(), 0, 0);
insert into testing.batch values(2, now(), 1, 1);

select row_to_json(row(batch_id)) from testing.batch;

or

select row_to_json(b) 
from (select * from testing.batch) b;

They only produce the following message, but no output:

Successfully run. Total query runtime: 70 msec.
2 rows affected.

Other client output of the latter:

{"batch_id":1,"max_record":0,"record_count":0,"creation_ts":"2019-03-26T16:44:34.338218"}
{"batch_id":2,"max_record":1,"record_count":1,"creation_ts":"2019-03-26T16:51:33.196218"}

Messages

DateAuthorSubject
2019-03-26 15:18:07+00PG Bug reporting formBUG #15716: pgadmin 4.3: row_to_json error
2019-03-26 15:49:20+00Anthony SotolongoRe: BUG #15716: pgadmin 4.3: row_to_json error