Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Date: 2013-07-18 19:26:05
Message-ID: CAHGQGwG+BNaBNLxQNVKVs67sE_v9COXbEMCwmpa303JLOpahmQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 19, 2013 at 2:45 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 07/18/2013 04:25 AM, Amit Kapila wrote:
>> On Thursday, July 18, 2013 12:38 AM Josh Berkus wrote:
>>> On 07/17/2013 12:01 PM, Alvaro Herrera wrote:
>>>> Both of these seem like they would make troubleshooters' lives more
>>>> difficult. I think we should just parse the auto file automatically
>>>> after parsing postgresql.conf, without requiring the include
>>> directive
>>>> to be there.
>>>
>>> Wait, I thought the auto file was going into the conf.d directory?
>>
>> Auto file is going into config directory, but will that make any difference
>> if we have to parse it automatically after postgresql.conf.
>
> Well, I thought that the whole conf.d directory automatically got parsed
> after postgresql.conf. No?

No, in the previous patch. We needed to set include_dir to 'config' (though
that's the default).

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2013-07-18 19:40:04 Re: Proposal/design feedback needed: WITHIN GROUP (sql standard ordered set aggregate functions)
Previous Message Alvaro Herrera 2013-07-18 19:21:15 Re: Fatal error after starting postgres : sys identifiers must be different