Re: Postgres won't start after setting ssl=on

From: Mike Christensen <mike(at)kitchenpc(dot)com>
To: 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: Re: Postgres won't start after setting ssl=on
Date: 2010-10-10 07:08:13
Message-ID: AANLkTinFc_5jtzFnYF7rO-7xwNN7=34qFcRNw=OSZrgf@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message issinyeung 2010-10-10 13:18:34 AAi.}c\1Re: Postgres won't start after setting ssl=on
Previous Message Scott Marlowe 2010-10-10 06:54:48 Re: Postgres won't start after setting ssl=on