Thread: BUG: CEST FATAL: unrecognized configuration parameter "application_name"

<div class="gmail_quote"><div class="gmail_quote"><div class="im"><span>I am getting following message in log
/var/log/postgresql/postgresql-8.2-main.log:</span><br/><span>CEST FATAL: unrecognized configuration parameter
"application_name"</span><br/><span><br />pgAdmin version: 1.12.1</span><br /></div><span>pgAdmin OS: Windows XP
SP3</span><br/><span>PostgreSQL version: 8.2</span><br /><span>PostgreSQL OS: Debian 5.0.4</span><br /><div
class="im"><span></span><br /></div><span>I have installed 1.10.5 too but it causes the same message.</span> This
messagecomes after installation of 1.12.1 using postgresql-9.0.1-1-windows.exe package.<div class="im"><br
/><span></span><br/><span>With the best regards,</span><br clear="all" /><span></span><font color="#888888">Milan
Jaroš</font><br/><font color="#888888"> </font></div></div><br /></div><br /> 

On Fri, Oct 15, 2010 at 8:33 AM, Milan Jaroš <milan.jaros@gmail.com> wrote:
> I am getting following message in log
> /var/log/postgresql/postgresql-8.2-main.log:
> CEST FATAL: unrecognized configuration parameter "application_name"
>
> pgAdmin version: 1.12.1
> pgAdmin OS: Windows XP SP3
> PostgreSQL version: 8.2
> PostgreSQL OS: Debian 5.0.4
>
> I have installed 1.10.5 too but it causes the same message. This message
> comes after installation of 1.12.1 using postgresql-9.0.1-1-windows.exe
> package.

They're harmless, but I'll bet you're not using the latest point
release of the 8.2 server. It shouldn't give out that message.


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

> They're harmless, but I'll bet you're not using the latest point
> release of the 8.2 server. It shouldn't give out that message.

A new feature was added in 9.0, to be able to specify an application
name. Because people using the 9.0 client lib might have problems when
connecting to an earlier version of the server, we back ported a patch
to earlier versions of the server that simply recognised the
application_name parameter as a valid parameter, but didn't actually
do anything with it. This was considered a bug fix under our release
policy. So if you install 8.2.18, this problem will go away, but it
probably isn't much of a problem anyway.


-- 
Regards,
Peter Geoghegan

Okay, thank you so much. We will update ASAP.<br /><br />RESOLVED<br /><br />Regards,<br clear="all" />Milan<br /><br
/><br/><div class="gmail_quote">On Fri, Oct 15, 2010 at 4:26 PM, Peter Geoghegan <span dir="ltr"><<a
href="mailto:peter.geoghegan86@gmail.com">peter.geoghegan86@gmail.com</a>></span>wrote:<br /><blockquote
class="gmail_quote"style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left:
1ex;"><divclass="im">> They're harmless, but I'll bet you're not using the latest point<br /> > release of the
8.2server. It shouldn't give out that message.<br /><br /></div>A new feature was added in 9.0, to be able to specify
anapplication<br /> name. Because people using the 9.0 client lib might have problems when<br /> connecting to an
earlierversion of the server, we back ported a patch<br /> to earlier versions of the server that simply recognised
the<br/> application_name parameter as a valid parameter, but didn't actually<br /> do anything with it. This was
considereda bug fix under our release<br /> policy. So if you install 8.2.18, this problem will go away, but it<br />
probablyisn't much of a problem anyway.<br /><br /><br /> --<br /> Regards,<br /><font color="#888888">Peter
Geoghegan<br/></font></blockquote></div><br />