Horton

Re: Configuration include directory

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Andrew Dunstan <andrew@dunslane.net>, Greg Jaskiewicz <gj@pointblue.com.pl>, Greg Smith <greg@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2011-11-17T16:03:45Z
Lists: 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