From: | Mike Christensen <mike(at)kitchenpc(dot)com> |
---|---|
To: | francisco(at)npgsql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Npgsql Exception |
Date: | 2010-08-23 23:38:22 |
Message-ID: | AANLkTikAYYpe1Q7+pRQRyOPewKvUjXQNUhr8jHFm=QkO@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Sounds good, I think I'll take Tom's advice.. Actually I'm planning
on waiting for the 9.0 release to upgrade, so in theory that should
just fix everything.. This only happens if I break on all exceptions,
which I usually have turned off.. Thanks!
Mike
On Mon, Aug 23, 2010 at 11:56 AM, Francisco Figueiredo Jr.
<francisco(at)npgsql(dot)org> wrote:
> Are you using Npgsql with NHibernate?
>
> We added an option to send this command when starting a connection.
>
> But the setting is inside a try catch error handler, so you aren't
> supposed to receive it.
>
> On my tests I couldn't reproduce the error. The only error we got
> about that was a user who had a breakpoint set in VS.net to trigger an
> exception whenever there was an error from server. But this was only
> while debugging his app, obviously.
>
>
> On Mon, Aug 23, 2010 at 10:49, 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
>>
>> --
>> 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
>>
>
>
>
> --
> Regards,
>
> Francisco Figueiredo Jr.
> Npgsql Lead Developer
> http://www.npgsql.org
> http://fxjr.blogspot.com
> http://twitter.com/franciscojunior
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Christensen | 2010-08-23 23:43:13 | Re: Npgsql Exception |
Previous Message | san man | 2010-08-23 23:07:08 | Re: select from pipe-delimited field |