Re: \if, \elseif, \else, \endif (was Re: PSQL commands:\quit_if, \quit_unless)

Поиск
Список
Период
Сортировка
От Corey Huinker
Тема Re: \if, \elseif, \else, \endif (was Re: PSQL commands:\quit_if, \quit_unless)
Дата
Msg-id CADkLM=czttdEn1fVMb-qAQDvteXU3SOv47GsKbea9+iaYbCK_w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] \if, \elseif, \else, \endif (was Re: PSQL commands:\quit_if, \quit_unless)  ("Daniel Verite" <daniel@manitou-mail.org>)
Ответы Re: \if, \elseif, \else, \endif (was Re: PSQL commands:\quit_if, \quit_unless)  (Fabien COELHO <coelho@cri.ensmp.fr>)
Список pgsql-hackers
Дерево обсуждения
On Mon, Mar 27, 2017 at 10:34 AM, Fabien COELHO <coelho@cri.ensmp.fr> wrote:

Hello,

I think that you could use another pattern where you init the
PQExpBufferData structure instead of create it, so that only the string is
malloced.

In v26, I have the functions return PQExpBuffer. The two calling functions
then free it, which should solve any leak.

 Yep, it works as well.

Here's an addendum that does that. I can combine them in v27, but figured
this was quicker.

 It works.

However having just one full patch with a number would help so that I can say "ready to committer" or not on something.

--
Fabien.

And here you go (sorry for the delay, had errands to run).


Вложения

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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: WIP: Faster Expression Processing v4
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: PL/Python: Add cursor and execute methods to planobject