Re: BUG #9896: Bug in FULL OUTER JOIN

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #9896: Bug in FULL OUTER JOIN
Дата
Msg-id 28747.1396901878@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: BUG #9896: Bug in FULL OUTER JOIN  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: BUG #9896: Bug in FULL OUTER JOIN
Список pgsql-bugs
I wrote:
> sqlpro@sqlspot.com writes:
>> SELECT *
>> FROM   T_CLIENT_CLI AS C
>> FULL OUTER JOIN T_PROSPECT_PSP AS P
>> ON C.CLI_SIREN = P.PSP_SIREN
>> OR C.CLI_ENSEIGNE = P.PSP_ENSEIGNE;

> Can you show us the query plans used by those systems?

For the archives' sake: the OP sent me a not-too-useful screen shot
in which SQL Server claims it's using a merge join for this query.

I find this less than credible: what linear sort order would bring
together all the potentially joinable rows?  If they're getting the
right answer at all, there must be some secret sauce in there someplace.
Perhaps they're just Doing It The Hard Way with state storage
proportional to the size of the relations?

            regards, tom lane

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

Предыдущее
От: klimm@lohn24.de
Дата:
Сообщение: BUG #9897: Wrong Julian Date through ODBC
Следующее
От: Vik Fearing
Дата:
Сообщение: Re: BUG #9896: Bug in FULL OUTER JOIN