Re: BUG #17745: RETURNING after INSERT does not return the same structure of response - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #17745: RETURNING after INSERT does not return the same structure of response
Date
Msg-id CAKFQuwZgvtcGqVOcbUjb3K7ipD19Ldm-UbwaWogkEWJ-smy2Kw@mail.gmail.com
Whole thread Raw
In response to BUG #17745: RETURNING after INSERT does not return the same structure of response  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Wednesday, January 11, 2023, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      17745
Logged by:          Paweł Podgórski
Email address:      pawel.jan.podgorski@gmail.com
PostgreSQL version: 14.5
Operating system:   Windows 11
Description:       

When I try to "INSERT INTO .... RETURNING (channel)" the output is:
   channel
--------------
 3o0mNjcS4CMr
(1 row)

But RETURNING multiple attributes produces another output:
"INSERT INTO .... RETURNING ( channel ,  last_processing_timestamp,
last_successful_processing_timestamp )"
                                     row
--------------------------------------------------------------------------------
 (3o0mNjcS4CMr,"2023-01-11 12:01:40.016988+01","2023-01-11
12:01:40.016988+01")
(1 row)

The output that is expected is similar to:
"INSERT INTO .... RETURNING channel ,  last_processing_timestamp,
last_successful_processing_timestamp "
   channel    |   last_processing_timestamp   |
last_successful_processing_timestamp
--------------+-------------------------------+--------------------------------------
 3o0mNjcS4CMr | 2023-01-11 12:01:40.016988+01 | 2023-01-11
12:01:40.016988+01
(1 row)


If you don’t want a composite returned don’t put parentheses around the column list.

David J.
 

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17745: RETURNING after INSERT does not return the same structure of response
Next
From: PG Bug reporting form
Date:
Subject: BUG #17746: Partitioning by hash of a text depends on icu version when text collation is not deterministic