Re: [HACKERS] Update comment in ExecPartitionCheck

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: [HACKERS] Update comment in ExecPartitionCheck
Дата
Msg-id CA+TgmoYs+6Ri+Hse0cxGNgEZqR0YigAD22uG3LGJihoc4Jri2w@mail.gmail.com
обсуждение исходный текст
Ответ на [HACKERS] Update comment in ExecPartitionCheck  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
Ответы Re: [HACKERS] Update comment in ExecPartitionCheck  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
Список pgsql-hackers
On Tue, Jul 4, 2017 at 4:55 AM, Etsuro Fujita
<fujita.etsuro@lab.ntt.co.jp> wrote:
> This comment in an error handling in ExecPartitionCheck():
>
>     if (!ExecCheck(resultRelInfo->ri_PartitionCheckExpr, econtext))
>     {
>         char       *val_desc;
>         Relation    orig_rel = rel;
>
>         /* See the comment above. */
>         if (resultRelInfo->ri_PartitionRoot)
>
> should be updated because we don't have any comment on that above in the
> code.  Since we have a comment on that in ExecConstraints() defined just
> below that function, I think the comment should be something like this: "See
> the comment in ExecConstraints().".  Attached is a patch for that.

Hrm.  I'm not sure I understand which comment in ExecConstraints()
this is supposed to refer to.  Maybe we need to think a bit harder
about how to make this clear.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] why not parallel seq scan for slow functions
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] [PATCH] Push limit to sort through a subquery