Re: Configuration include directory - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Configuration include directory
Date
Msg-id 12705.1321545825@sss.pgh.pa.us
Whole thread Raw
In response to Re: Configuration include directory  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Configuration include directory  (Greg Smith <greg@2ndQuadrant.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Excerpts from Tom Lane's message of mié nov 16 22:52:35 -0300 2011:
>> (Do we guard against recursive inclusion via plain old include?  If
>> not, maybe this isn't worth worrying about.)

> Yes, we do

> FATAL:  could not open configuration file "foo.conf": maximum nesting depth exceeded

Oh, right.  So as long as the include-directory code path doesn't
interfere with tracking that nesting depth, I don't think it needs
any extra protection against include-the-same-directory.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Removing postgres -f command line option
Next
From: Robert Haas
Date:
Subject: Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement