Re: struct RelOptInfo member relid comments

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: struct RelOptInfo member relid comments
Дата
Msg-id 585848.1716528533@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: struct RelOptInfo member relid comments  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
Список pgsql-hackers
Ashutosh Bapat <ashutosh.bapat.oss@gmail.com> writes:
> OJ is an outer join, AFAIU. OJ's have their own relids. If you are
> wondering why not all joins - I think inner joins need not be tracked as
> separated relations in parse tree, but OJ's need to be.

An outer join is necessarily associated with explicit JOIN syntax
in the FROM clause, and each such JOIN has its own rangetable entry
and hence a relid.  Inner joins might arise from comma syntax
(that is, "SELECT ... FROM tab1, tab2").  For perhaps-historical
reasons that syntax doesn't give rise to an explicit RTE_JOIN
rangetable entry, so the implied join has no relid.

            regards, tom lane



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

Предыдущее
От: Ashutosh Bapat
Дата:
Сообщение: Re: struct RelOptInfo member relid comments
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: Avoid possible dereference null pointer (src/backend/catalog/pg_depend.c)