Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it
Дата
Msg-id CAA4eK1Jp+t6eEzDH1FYdqcnLpaZbu2q7Qk=EVWOLJghJv9TeeA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On Fri, Jan 17, 2014 at 12:16 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> PS: off topic, but isn't ParseConfigDirectory leaking the result
> of AbsoluteConfigLocation?  In both normal and error paths?

   Yes, I also think it leaks in both cases and similar leak is
   present in ParseConfigFile(). I have tried to fix both of these
   leaks with attached patch.

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

Вложения

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

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: Heavily modified big table bloat even in auto vacuum is running
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: Backup throttling