Re: possible bug

Alberto Rodriguez Galdo wrote:

> This is the stackTrace:
>
> org.postgresql.util.PSQLException: ERROR: invalid message format
> at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1471)
> at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1256)
> at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:175)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:389)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:314)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:306)

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)

-O