Re: [BUGS] BUG #2249: unsupported frontend protocol

2006-02-09 Thread Kris Jurka



On Thu, 9 Feb 2006, Satheesh wrote:


The following bug has been logged online:

Bug reference:  2249
PostgreSQL version: 7.3.2
Description:unsupported frontend protocol
Details:

iam having database server postgres version 7.3.2 and jboss 4.x as 
webserver, while executing the application iam getting an error message 
of "FATAL:Unsupported Front end Protocol". This makes my application to 
execute slowly. plz help me. Tahnks in Advance




When using a new JDBC driver with an old server version it first tries to 
connect with the v3 protocol and then falls back to the v2 protocol if 
that fails.  To tell the driver you want a v2 protocol from the start add 
?protocolVersion=2 to your URL.


Kris Jurka


---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [BUGS] BUG #2249: unsupported frontend protocol

2006-02-09 Thread Tom Lane
"Satheesh" <[EMAIL PROTECTED]> writes:
> iam having database server postgres version 7.3.2 and jboss 4.x as
> webserver, while executing the application iam getting an error message of
> "FATAL:Unsupported Front end Protocol". This makes my application to execute
> slowly. plz help me. Tahnks in Advance

You probably need 7.4 or later Postgres.

regards, tom lane

---(end of broadcast)---
TIP 6: explain analyze is your friend


[BUGS] BUG #2249: unsupported frontend protocol

2006-02-09 Thread Satheesh

The following bug has been logged online:

Bug reference:  2249
Logged by:  Satheesh
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.3.2
Operating system:   Red hat Linux 9
Description:unsupported frontend protocol
Details: 

hi,

iam having database server postgres version 7.3.2 and jboss 4.x as
webserver, while executing the application iam getting an error message of
"FATAL:Unsupported Front end Protocol". This makes my application to execute
slowly. plz help me. Tahnks in Advance


satheesh

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly