Re: [HACKERS] Re: issue: record or row variable cannot be part ofmultiple-item INTO list - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] Re: issue: record or row variable cannot be part ofmultiple-item INTO list
Date
Msg-id CAFj8pRBVL_NsH2DVt1z9sVzyznHAp2Nx9-yoGMCgRFP7t=2k5w@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Re: issue: record or row variable cannot be part of multiple-itemINTO list  (Anthony Bykov <a.bykov@postgrespro.ru>)
Responses [HACKERS] Re: issue: record or row variable cannot be part of multiple-itemINTO list
Re: [HACKERS] Re: issue: record or row variable cannot be part of multiple-item INTO list
List pgsql-hackers
Hi

2017-09-14 12:33 GMT+02:00 Anthony Bykov <a.bykov@postgrespro.ru>:
The following review has been posted through the commitfest application:
make installcheck-world:  tested, passed
Implements feature:       tested, passed
Spec compliant:           not tested
Documentation:            tested, failed

Hello,
As far as I understand, this patch adds functionality (correct me if I'm wrong) for users. Shouldn't there be any changes in doc/src/sgml/ with the description of new functionality?

It removes undocumented limit. I recheck plpgsql documentation and there are not any rows about prohibited combinations of data types.

There is line:

where command-string is an expression yielding a string (of type text) containing the command to be executed. The optional target is a record variable, a row variable, or a comma-separated list of simple variables and record/row fields, into which the results of the command will be stored. The optional USING expressions supply values to be inserted into the command.

what is correct if I understand well with this patch.

Regards

Pavel
 

Regards
Anthony

The new status of this patch is: Waiting on Author

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: [HACKERS] Challenges preventing us moving to 64 bit transactionid (XID)?
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] psql: new help related to variables are not tooreadable