Re: Exception from deadlock - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: Exception from deadlock
Date
Msg-id BB148208-D51D-4C2D-BC38-9B2FC98E931F@fastcrypt.com
Whole thread Raw
In response to Re: Exception from deadlock  (Kris Jurka <books@ejurka.com>)
List pgsql-jdbc
Kris,

I think as much as possible makes sense too, this shouldn't be in the
critical path for performance, so why not ?

Dave
On 8-Jul-05, at 8:58 PM, Kris Jurka wrote:


>
>
> On Thu, 7 Jul 2005, Oliver Jowett wrote:
>
>
>
>> Joseph Shraibman wrote:
>>
>>
>>
>>> So my quesion is where did that detail information go in the jdbc
>>> driver?
>>>
>>> I'm using postgres 7.4.7 with the jdbc driver that comes with it.
>>>
>>>
>>
>> Can you try an 8.0-era driver from jdbc.postgresql.org? There have
>> been
>> a number of changes to server error message handling since 7.4.
>>
>>
>>
>
> Actually this is the same in 7.4 and later versions.  The level of
> detail
> put into the exception message is derived from the loglevel URL
> parameter,
> see the toString method.
>
> http://gborg.postgresql.org/project/pgjdbc/cvs/co.php/pgjdbc/org/
> postgresql/util/ServerErrorMessage.java?r=1.8
>
> Later driver versions (8.1dev) allow pg specific code to access all
> of the
> fields individually to craft any message they desire.
>
> I personally like the idea of putting more information into the
> default
> error message.  How much more do people want?
>
> http://www.postgresql.org/docs/8.0/static/protocol-error-fields.html
>
> Kris Jurka
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
>
>



Dave Cramer
davec@postgresintl.com
www.postgresintl.com
ICQ #14675561
jabber davecramer@jabber.org
ph (519 939 0336 )



pgsql-jdbc by date:

Previous
From: peter royal
Date:
Subject: Re: Exception from deadlock
Next
From: Oliver Jowett
Date:
Subject: Re: Exception from deadlock