Skip site navigation (1) Skip section navigation (2)

Re: possible bug

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Alberto Rodriguez Galdo <argaldo(at)gmail(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: possible bug
Date: 2005-04-28 00:40:06
Message-ID: (view raw or whole thread)
Lists: pgsql-jdbc
Alberto Rodriguez Galdo wrote:

> This is the stackTrace:
> org.postgresql.util.PSQLException: ERROR: invalid message format
>         at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(
>         at org.postgresql.core.v3.QueryExecutorImpl.processResults(
>         at org.postgresql.core.v3.QueryExecutorImpl.execute(
>         at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(
>         at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(
>         at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(

Can't reproduce this against 8.0.0 with the build 310 jar. Testcase
attached. What are you doing differently to this testcase? The schema I
used (in case it wasn't an error at the Parse stage) is:

test=# \d backupitem
     Table "public.backupitem"
    Column    |  Type   | Modifiers
 idbackup     | integer |
 pathservidor | text    |
 pathoriginal | text    |
 hash         | text    |
 esenlace     | text    |
 metadatos    | text    |

You might want to try appending '?loglevel=2' to your connection URL;
that should generate screeds of debugging to stderr that may be useful
in debugging this. (send it to me off-list if it's large)


Description: text/plain (1.3 KB)

In response to

  • possible bug at 2005-04-27 23:43:58 from Alberto Rodriguez Galdo

pgsql-jdbc by date

Next:From: Gnanavel SDate: 2005-04-28 03:51:26
Subject: Performance of loop
Previous:From: Alberto Rodriguez GaldoDate: 2005-04-27 23:43:58
Subject: possible bug

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group