Re: Mammoth in Core?

Поиск
Список
Период
Сортировка
От Takahiro Itagaki
Тема Re: Mammoth in Core?
Дата
Msg-id 20100125142812.9171.52131E4D@oss.ntt.co.jp
обсуждение исходный текст
Ответ на Re: Mammoth in Core?  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Clustering Docs WAS: Mammoth in Core?  (Josh Berkus <josh@agliodbs.com>)
Список pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> It's going to be a really, really, *really* hard sell to get us to
> export any sort of external API to the parser internals.  At least
> if by "API" you mean something other than "we will whack this around
> to an indefinite degree on no notice, and don't even think about
> complaining".
> 
> What exactly is the goal that you think such a thing would serve,
> anyway?  The fragments on the referenced web page don't leave me with
> any warm feelings about how well the idea has been thought through.

Some of items in the referenced web page are just voted results form cluster
projects. At this time, we should read them as "what is needed", but not
"how to do it". They have been not reviewd yet and not well-considered
to be official TODO items.

I知 not sure what pgpool team think about, but I do NOT intend to export the
existing internal functions as-is. As for my personal goal, I think pgpool
should be re-implemented on the layers of SQL/MED FDW or planner/executor hooks.
I'd say the SQL/MED FDW apporach is "one by one into core (from projects)",
and the hook apporach is "external API (from core)".

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center




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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO on inherited columns
Следующее
От: Scott Bailey
Дата:
Сообщение: Re: Review: listagg aggregate