From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
Cc: | David Christensen <david(at)endpoint(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Patch for 9.1: initdb -C option |
Date: | 2010-07-23 04:00:09 |
Message-ID: | AANLkTim1y2iVUeUAMxPy+gnVjRVukG71V6mb8B4GoqRv@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/7/22 KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>:
> Anyway, it is an obvious feature, and seems to me works fine.
So this makes it sound like you like the feature.
> However, it is not clear for me how do we make progress this feature.
> If we support a command to include other configuration, it also needs
> to patch on the postgresql backend, not only initdb.
I don't know what this means.
> In my personal opinion, as long as you don't need any special configuration
> under the single user mode or bootstraping mode launched by initdb,
> we can modify it using shell script or others later.
But here it sounds like you're saying we don't need the feature
because may as well just edit postgresql.conf by hand.
So I'm confused.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | KaiGai Kohei | 2010-07-23 04:10:36 | Re: Patch for 9.1: initdb -C option |
Previous Message | Robert Haas | 2010-07-23 03:56:36 | Re: security label support, part.2 |