plpgsql - additional extra checks

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: plpgsql - additional extra checks
Date: 2017-01-11 13:54:35
Message-ID: CAFj8pRA2kKRDKpUNwLY0GeG1OqOp+tLS2yQA1V41gzuSz-hCng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

Hi

I am starting new thread for this patch (related to merging some ideas from
plpgsql2 project thread).

Here is simple patch with two new extra_warnings, extra_errors checks

1. strict_multi_assignment - checks the number of target variables and
source values.
2. too_many_rows - checks if returned rows is more than one

The extra checks are designed to help identify some possible errors or
issues. It is not way how to change a design, behave and features of
plpgsql language.

Now, the extra checks are three fields only - it is easy maintainable now,
and I don't see a necessity to implement some another management for extra
checks.

Regards

Pavel

Attachment Content-Type Size
plpgsql_extra_runtime_checks-01.patch text/x-patch 9.7 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2017-01-11 14:05:05 Re: WARM and indirect indexes
Previous Message Beena Emerson 2017-01-11 13:43:15 Re: Re: Clarifying "server starting" messaging in pg_ctl start without --wait