Re: pgsql: Add strict_multi_assignment and too_many_rows plpgsql checks

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: pgsql: Add strict_multi_assignment and too_many_rows plpgsql checks
Дата
Msg-id CAFj8pRAUgAhgc=z_RasOuv+-gTPCocd-uXdw=L_orVv8T7cUyA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pgsql: Add strict_multi_assignment and too_many_rows plpgsqlchecks  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
Hi

čt 9. 5. 2019 v 8:52 odesílatel Peter Eisentraut <peter.eisentraut@2ndquadrant.com> napsal:
On 2018-07-25 01:47, Tomas Vondra wrote:
> Add strict_multi_assignment and too_many_rows plpgsql checks

Could you clarify this error message:

    /* translator: %s represents a name of an extra check */
    errdetail("%s check of %s is active.",
             "strict_multi_assignment",
             strict_multiassignment_level == ERROR ? "extra_errors" :
                                                 "extra_warnings"),

What does, for example,

    strict_multi_assignment check of extra_errors is active.

mean?


strict_multi_assignment is a name of plpgsql extra check. This check checks number of expressions against number of target variables.
extra checks can produces errors or warnings - so second placeholder specifies used level.

The sense of this detail's message is a introduce of reason of this error message.

Regards

Pavel
 
Also note that the translator comment is only mentioning one of the %s.

--
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Masahiko Sawada
Дата:
Сообщение: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and KeyManagement Service (KMS)
Следующее
От: Etsuro Fujita
Дата:
Сообщение: Re: postgres_fdw: another oddity in costing aggregate pushdown paths