Re: ALTER SYSTEM SET command to change postgresql.conf parameters
От | Robert Haas |
---|---|
Тема | Re: ALTER SYSTEM SET command to change postgresql.conf parameters |
Дата | |
Msg-id | CA+TgmoZXAKLz-HBZA-F7z4uWZt8HQwE933jBmzqHWGngrZ0F6Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: ALTER SYSTEM SET command to change postgresql.conf parameters
|
Список | pgsql-hackers |
On Mon, Jan 6, 2014 at 9:48 AM, Amit Kapila <amit.kapila16@gmail.com> wrote: >> Couldn't we also handle this by postponing FreeConfigVariables until >> after the if (error) block? > > Wouldn't doing that way can lead to bigger memory leak, if error level > is ERROR. Though in current fix also it can leak memory but it will be > just for ErrorConfFile_save. I think some similar case can happen for > 'pre_value' in code currently as well, that's why I have fixed it in a > similar way in patch. I was assuming that error-recovery would reset the containing memory context, but I'm not sure what memory context we're executing in at this point. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: