Re: [HACKERS] Oops, I seem to have changed UNION's behavior

Поиск
Список
Период
Сортировка
Искать
От
Taral
Тема
Re: [HACKERS] Oops, I seem to have changed UNION's behavior
Дата
в 16:52:53
Msg-id
Pine.LNX.4.10.9905091551330.8677-100000@dragon.taral.net
Ответ на
Список
Дерево обсуждения
Oops, I seem to have changed UNION's behavior Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] Oops, I seem to have changed UNION's behavior Bruce Momjian <maillist@candle.pha.pa.us>
Re: [HACKERS] Oops, I seem to have changed UNION's behavior Bruce Momjian <maillist@candle.pha.pa.us>
Re: [HACKERS] Oops, I seem to have changed UNION's behavior Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] Oops, I seem to have changed UNION's behavior Oleg Broytmann <phd@sun.med.ru>
On Sun, 9 May 1999, Thomas Lockhart wrote:

> > > Am I right in thinking that UNION (without ALL) is defined to do a
> > > DISTINCT on its result, so that duplicates are removed even if the
> > > duplicates both came from the same source table?  That's what 6.4.2
> > > does, but I do not know if it's strictly kosher according to the SQL
> > > spec.
> 
> Yes, this is the right behavior according to SQL92...

In which case something should put a DISTINCT on queries using UNION...
since making T_Query nodes never equal is a deoptimization.

Taral


В списке pgsql-hackers по дате отправления
От: Taral
Дата:
От: Thomas Lockhart
Дата:
FAQ