Re: [HACKERS] plpgsql - additional extra checks - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: [HACKERS] plpgsql - additional extra checks
Date
Msg-id CAL9smLBbkjtHCK5hyRtAGByAnZD1h4S6Qa_N-eEsnXrEZcdpSA@mail.gmail.com
Whole thread Raw
In response to [HACKERS] plpgsql - additional extra checks  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [HACKERS] plpgsql - additional extra checks  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Wed, Jan 11, 2017 at 2:54 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
1. strict_multi_assignment - checks the number of target variables and source values.

I've proposed this before (maybe around a year ago), except the checks were done at parse time, rather than runtime.  I much prefer that approach.  If I recall correctly, the patch was considered to be good, but not good enough since it didn't handle all contexts (perhaps FOR loop were missing, or something; I forget).
 
2. too_many_rows - checks if returned rows is more than one

I've also proposed this, and it was rejected because it was a runtime check, and some people don't like runtime checks.


.m

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: [HACKERS] WARM and indirect indexes
Next
From: Ashutosh Sharma
Date:
Subject: Re: [HACKERS] pageinspect: Hash index support