Re: Let's get rid of SPI_push/SPI_pop

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: Let's get rid of SPI_push/SPI_pop
Дата
Msg-id CAFj8pRBT9ZY2ccGbZNPhFheEmkLOEmENtX7ESBYx5=VLD5u8+Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Let's get rid of SPI_push/SPI_pop  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers


2016-11-07 15:47 GMT+01:00 Tom Lane <tgl@sss.pgh.pa.us>:
Pavel Stehule <pavel.stehule@gmail.com> writes:
> 2016-11-07 2:16 GMT+01:00 Tom Lane <tgl@sss.pgh.pa.us>:
>> So I think we should just delete these functions and adjust SPI_connect
>> and SPI_finish so that they just push/pop a context level unconditionally.
>> (Which will make them simpler, not more complicated.)

> cannot be there some performance impacts?

Any impact will be for the better, since we're removing logic.
I haven't gone through it in detail, but it might be as simple
as removing _SPI_curid and code that manipulates it.

ok

Pavel
 

                        regards, tom lane

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Add PGDLLEXPORT to PG_FUNCTION_INFO_V1
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: Detect supported SET parameters when pg_restore is run