Re: Npgsql Exception

From: Mike Christensen <mike(at)kitchenpc(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, francisco(at)npgsql(dot)org
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Npgsql Exception
Date: 2010-08-23 23:43:13
Message-ID: AANLkTinJ3cLgNB9_AHyBdetU=YQTeeJR9g03skQpEv26@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

BTW, version is:

'PostgreSQL 8.3.4, compiled by Visual C++ build 1400'

I don't have any such setting referenced in any .conf file. So I
guess NHibernate tries to set this setting, assuming I have a more
recent version of PG. If that's the case, it'll go away when I
upgrade..

Mike

On Mon, Aug 23, 2010 at 6:49 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Mike Christensen <mike(at)kitchenpc(dot)com> writes:
>> Sorry, when I had emailed the NHibernate DL the exception was in the
>> subject line.  I forgot to copy the subject this time.  The exception
>> is:
>
>> ERROR: 42704: unrecognized configuration parameter
>> "ssl_renegotiation_limit"
>
> ssl_renegotiation_limit is a server parameter that was added to all
> active PG branches in a security patch last February.  Apparently you
> have a postgresql.conf file that tries to set that parameter, and have
> reverted to a server version that doesn't include it.  Best fix is to
> update your PG to latest minor release.  Alternatively you could take
> out the setting but that would imply you don't have the security fix,
> and also probably the problem that led you to put in the setting would
> come back.
>
>                        regards, tom lane
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-08-24 00:08:40 Re: Warm Standby and resetting the primary as a standby
Previous Message Mike Christensen 2010-08-23 23:38:22 Re: Npgsql Exception