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

Re: Parsing config files in a directory

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: jd(at)commandprompt(dot)com
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Thom Brown <thombrown(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parsing config files in a directory
Date: 2009-10-29 17:13:57
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> In regards to parsing files in a directory. It makes sense. Why the
> implementation is so difficult is beyond me. Can't we just look at
> Apache and say, "Gee, it may not be perfect but it does everything we
> need, let's use their implementation."?

Reading files in a directory does not seem too hard, IIUC Magnus already
implemented it. What's hard is to convince anyone it helps solving the
tool editing problem (call it SET GLOBAL if you want).


In response to

pgsql-hackers by date

Next:From: Dimitri FontaineDate: 2009-10-29 17:18:17
Subject: Re: about GiST indexes
Previous:From: Hannu KrosingDate: 2009-10-29 16:59:01
Subject: Re: [PATCHES] updated hash functions for postgresql v1

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