Re: Introduce new multi insert Table AM and improve performance of various SQL commands with it for Heap AM

Поиск
Список
Период
Сортировка
От Jeff Davis
Тема Re: Introduce new multi insert Table AM and improve performance of various SQL commands with it for Heap AM
Дата
Msg-id 23a29125a2d07f96d49f97c31fcdb09a7f0ff6c1.camel@j-davis.com
обсуждение исходный текст
Ответ на Re: Introduce new multi insert Table AM and improve performance of various SQL commands with it for Heap AM  (Jeff Davis <pgsql@j-davis.com>)
Ответы Re: Introduce new multi insert Table AM and improve performance of various SQL commands with it for Heap AM
Список pgsql-hackers
On Mon, 2024-08-26 at 14:18 -0700, Jeff Davis wrote:
> 0001 implementation issues:
>
> * We need default implementations for AMs that don't implement the
> new
> APIs, so that the AM will still function even if it only defines the
> single-tuple APIs. If we need to make use of the AM's multi_insert
> method (I'm not sure we do), then the default methods would need to
> handle that as well. (I thought a previous version had these default
> implementations -- is there a reason they were removed?)

On second thought, it would be easier to just have the caller check
whether the AM supports the multi-insert path; and if not, fall back to
the single-tuple path. The single-tuple path is needed anyway for cases
like before-row triggers.

Regards,
    Jeff Davis




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