diff options
| author | Tomas Vondra <tomas.vondra@postgresql.org> | 2018-07-25 01:09:03 +0200 |
|---|---|---|
| committer | Tomas Vondra <tomas.vondra@postgresql.org> | 2018-07-25 01:46:32 +0200 |
| commit | 167075be3ab1547e186096bb8e6e448cd8eea5af (patch) | |
| tree | bf406f5eb63f2ea68c60c673d832a95c903c0c8d /src/backend/access/gist/gistutil.c | |
| parent | 2d3067595299d2ac1f29bbc26a83a99d59b33d4e (diff) | |
| download | postgresql-167075be3ab1547e186096bb8e6e448cd8eea5af.tar.gz postgresql-167075be3ab1547e186096bb8e6e448cd8eea5af.zip | |
Add strict_multi_assignment and too_many_rows plpgsql checks
Until now shadowed_variables was the only plpgsql check supported by
plpgsql.extra_warnings and plpgsql.extra_errors. This patch introduces
two new checks - strict_multi_assignment and too_many_rows. Unlike
shadowed_variables, these new checks are enforced at run-time.
strict_multi_assignment checks that commands allowing multi-assignment
(for example SELECT INTO) have the same number of sources and targets.
too_many_rows checks that queries with an INTO clause return one row
exactly.
These checks are aimed at cases that are technically valid and allowed,
but are often a sign of a bug. Therefore those checks are expected to
be enabled primarily in development and testing environments.
Author: Pavel Stehule
Reviewed-by: Stephen Frost, Tomas Vondra
Discussion: https://www.postgresql.org/message-id/flat/CAFj8pRA2kKRDKpUNwLY0GeG1OqOp+tLS2yQA1V41gzuSz-hCng@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions