Skip site navigation (1) Skip section navigation (2)

Re: Configuration include directory

From: Greg Smith <greg(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Greg Jaskiewicz <gj(at)pointblue(dot)com(dot)pl>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Configuration include directory
Date: 2011-12-07 11:05:18
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On 11/17/2011 11:03 AM, Tom Lane wrote:
> 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.

That was the theory in Magnus's original patch, and I don't believe 
anything has broken that part; I did glance at it.  Since I have a pile 
of good feedback from Noah now, I'll specifically test this as part of 
submitting the next patch update.

Greg Smith   2ndQuadrant US    greg(at)2ndQuadrant(dot)com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support

In response to

pgsql-hackers by date

Next:From: Peter GeogheganDate: 2011-12-07 11:57:08
Subject: Re: Inlining comparators as a performance optimisation
Previous:From: Jan UrbaƄskiDate: 2011-12-07 10:41:03
Subject: Re: [COMMITTERS] pgsql: plpython: Add SPI cursor support

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group