Postgres Pro
Downloads
Home   >   mailing lists

Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it
Date
Msg-id CAA4eK1Jp+t6eEzDH1FYdqcnLpaZbu2q7Qk=EVWOLJghJv9TeeA@mail.gmail.com
Whole thread Raw
In response to Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it
List pgsql-hackers
Tree view 
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
Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Heavily modified big table bloat even in auto vacuum is running
Next
From: Michael Paquier
Date:
Subject: Re: Backup throttling