| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "David Christensen" <david(at)endpoint(dot)com> |
| Cc: | "KaiGai Kohei" <kaigai(at)ak(dot)jp(dot)nec(dot)com>, "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Patch for 9.1: initdb -C option |
| Date: | 2010-07-20 22:33:34 |
| Message-ID: | 4C45DDEE0200002500033A19@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Christensen <david(at)endpoint(dot)com> wrote:
> On Jul 20, 2010, at 5:00 PM, Kevin Grittner wrote:
>> my shop has chosen to never touch the default postgresql.conf
>> file any more, beyond adding one line to the bottom of it which
>> is an include directive, to bring in our overrides.
> So you'll now issue:
>
> $ initdb ... -C 'include localconfig.conf' ? :-)
Yeah, that would cover us. I'm wondering if it is flexible enough
to serve everyone else so well. I hesitate to suggest it, but
perhaps it would, in combination with the include directive
supporting a directory name to mean all files in the directory? Or
maybe if it supported wildcards?
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-07-20 23:52:42 | Re: dynamically allocating chunks from shared memory |
| Previous Message | Andrew Dunstan | 2010-07-20 22:31:41 | Re: antisocial things you can do in git (but not CVS) |