Re: A query planner that learns

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: A query planner that learns
Дата
Msg-id 20061016210046.GD27790@alvh.no-ip.org
обсуждение исходный текст
Ответ на Re: A query planner that learns  (Madison Kelly <linux@alteeve.com>)
Ответы Re: A query planner that learns  (Madison Kelly <linux@alteeve.com>)
Список pgsql-general
Madison Kelly wrote:
> Alvaro Herrera wrote:
> >Jochem van Dieten wrote:
> >>Scott Marlowe wrote:
> >>>While all the talk of a hinting system over in hackers and perform is
> >>>good, and I have a few queries that could live with a simple hint system
> >>>pop up now and again, I keep thinking that a query planner that learns
> >>>from its mistakes over time is far more desirable.
> >>>Is it reasonable or possible for the system to have a way to look at
> >>>query plans it's run and look for obvious mistakes its made, like being
> >>>off by a factor of 10 or more in estimations, and slowly learn to apply
> >>>its own hints?
> >>Technically it is very feasible. But I think you might want to check US
> >>Patent 6,763,359 before you start writing any code.
> >
> >I think it would be a very good idea if you guys stopped looking at the
> >US patent database.  It does no good to anyone.  There's no way we can
> >avoid stomping on a patent or another -- there are patents for everything.
>
> Hasn't IBM release a pile of it's patents for use (or at least stated
> they won't sue) to OSS projects? If so, is this patent covered by that
> "amnesty"?

This is useless as a policy, because we have plenty of companies basing
their proprietary code on PostgreSQL, which wouldn't be subject to the
grant (EnterpriseDB, Command Prompt, Fujitsu, SRA).  We do support them.


> Simply ignoring patents because "there is a patent for everything" is a
> recipe for disaster. Companies like MS are running out of ways to tear
> open OSS and they are certainly not above (below?) suing the heck out of
> OSS projects for patent infringement.

It has been said that unknowingly infringing a patent is much less
problematic than knowingly doing same.  We don't have the manpower to
implement the whole Postgres without infringing a single patent, so the
best approach is to refrain from researching possible patents applying
to us in the first place.

If people comes here and points at patents that we infringe or may
infringe, it will cause much more (useless) work for hackers which then
have to search alternative ways of doing the same things.


> What's needed is reform in the USPO. Call you congress (wo)man and
> complain, but don't flaunt the law; you will lose.

I agree.  However, I am not an US inhabitant in the first place, and
bless my parents for that.  Heck, I was even denied a visa -- twice.
Please do us all a favor and write to your congresspeople.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: pg_locks: who is locking ?
Следующее
От: Madison Kelly
Дата:
Сообщение: Re: A query planner that learns