| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Smith <gsmith(at)gregsmith(dot)com> |
| Cc: | Chuck <chuckr(at)velofish(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: basic questions: Postgres with yum on CentOS 5.1 |
| Date: | 2008-01-02 05:35:57 |
| Message-ID: | 9847.1199252157@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Greg Smith <gsmith(at)gregsmith(dot)com> writes:
> On Tue, 1 Jan 2008, Chuck wrote:
>> Since I have a packaged installation, I don't believe that I will call
>> initdb directly.
> There is actually another command I don't think you've noticed yet:
> service postgresql initdb
Actually, that was only added in very recent versions of the postgresql
init script. Before about 8.2, the first 'service postgresql start'
would automatically run initdb. We split it out because of the (small)
risk of doing the wrong thing ...
In any case, I concur with the suggestion that you should use the init
script rather than invoking initdb directly. In most package setups
that's much more likely to get the details right.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-01-02 05:36:42 | Re: visibility rules for AFTER UPDATE Constraint Triggers Function |
| Previous Message | Richard Broersma Jr | 2008-01-02 05:25:12 | visibility rules for AFTER UPDATE Constraint Triggers Function |