On Wed, Sep 14, 2011 at 02:40:15AM +0100, Thom Brown wrote:
> On 13 September 2011 15:17, Tom Lane wrote:
> > Thom Brown writes:
> >> There appears to be a problem with starting Postgres if the SSL key
> >> has a passphrase on it.
> >
> > It's documented that that's unsupported. Given the number
On 13 September 2011 15:17, Tom Lane wrote:
> Thom Brown writes:
>> There appears to be a problem with starting Postgres if the SSL key
>> has a passphrase on it.
>
> It's documented that that's unsupported. Given the number of ways to
> start a postmaster, and the fact that many of them are non
On 13 September 2011 15:17, Tom Lane wrote:
> Thom Brown writes:
>> There appears to be a problem with starting Postgres if the SSL key
>> has a passphrase on it.
>
> It's documented that that's unsupported. Given the number of ways to
> start a postmaster, and the fact that many of them are non
Thom Brown writes:
> There appears to be a problem with starting Postgres if the SSL key
> has a passphrase on it.
It's documented that that's unsupported. Given the number of ways to
start a postmaster, and the fact that many of them are noninteractive,
I don't think it's very productive for us
Hi,
There appears to be a problem with starting Postgres if the SSL key
has a passphrase on it. The following happens:
Enter PEM pass phrase:
FATAL: could not load private key file "server.key": problems getting password
Starting with "postgres -D /path/to/cluster" returns:
Enter PEM pass phr
