From: | issinyeung(at)gmail(dot)com |
---|---|
To: | Mike Christensen <mike(at)kitchenpc(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | Darren Duncan <darren(at)darrenduncan(dot)net>, " pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | AAi.}c\1Re: Postgres won't start after setting ssl=on |
Date: | 2010-10-10 13:18:34 |
Message-ID: | y44mnsjfpu4673qga54e5qdv.1286716659660@email.android.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
coh乡w
Mike Christensen <mike(at)kitchenpc(dot)com>编写:
>While I do appreciate the vote of confidence, rest assured you will
>never see a post from me that starts with "So I've been hacking the pg
>code and..."
>
>On Sat, Oct 9, 2010 at 11:54 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
>> On Sat, Oct 9, 2010 at 10:04 PM, Darren Duncan <darren(at)darrenduncan(dot)net> wrote:
>>> The owner of these new files needs to be the same as that of your Pg data
>>> dir in general or postgresql.conf specifically, and that owner be the same
>>> as the process that runs the Pg server. Are you running Pg as root? (In
>>> any event, you should have another user; running programs or servers as root
>>> when they don't need root powers is generally a bad idea.) -- Darren Duncan
>>
>> Actually, unless you've hacked the pg code, it won't start as root.
>>
>
>--
>Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-general
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Sargent | 2010-10-10 15:40:23 | Re: Postgres won't start after setting ssl=on |
Previous Message | Mike Christensen | 2010-10-10 07:08:13 | Re: Postgres won't start after setting ssl=on |