Re: JDBC error in 7.0.3 - Mailing list pgsql-general

From Travis Bauer
Subject Re: JDBC error in 7.0.3
Date
Msg-id 20010417111052.A19904@ghost.cs.indiana.edu
Whole thread Raw
In response to Re: JDBC error in 7.0.3  (Peter T Mount <peter@retep.org.uk>)
List pgsql-general
Thanks for the reply.  I figured it out.  The previous insert
statement before this one was including unusual character codes
as part of a string.  This was confusing the postmaster, which would
stop interpreting that sql statement at that character and then
for some reason confuse the next statements as part of the
previous one.  I'm not sure why this is.  I fixed the problem by
having my program "wash" all strings so no unusual characters
get through.  If you'd like to puruse this issue further I can
send you the offending string, but I have fixed this particular
problem for my purposes.

--
----------------------------------------------------------------
Travis Bauer | CS Grad Student | IU |www.cs.indiana.edu/~trbauer
----------------------------------------------------------------

Peter T Mount (peter@retep.org.uk) wrote:

> Quoting Travis Bauer <trbauer@indiana.edu>:
>
> > During the run of a java program connected to 7.0.3, the following
> > errors occurred:
> >
> > insert into current_resources values (459, 0,
> > 'http://a1829.g.akamaitech.net/6/1829/792/000/search.britannica.com/
> > images/storethumbs/T_CMB_HG_FDALRTP.jpg', '', '', 'not foundnot found
> > the requested object does not exist on this server the link you followed
> >
> > is either outdated inaccurate or the server has been instructed not to
> > let
> > you have it please inform the site administrator of the referring page
> > r',
> > 'Not Found')
> > ERROR: Unterminated quotes string
> >
> > Error updating: insert into current_usages values (115, 459, 'trbauer',
> >
> > CURRENT_TIMESTAMP, 0) -- java.sql.SQLException:
> > FATAL 1:  Socket command type r unknown
> >
> > Any subsequent attent to access the database yields:
> >
> > An I/O error has occured while flushing the output -
> > java.io.IOException:
> > Broken pipe
> >
> > The problem is that the first insert statement is correct.  Other
> > statements
> > had proceeded it.  Could one of them have been the problem?
>
> No, the SQL looks ok. The broken pipe exceptions seem to indicate that the
> backend is dying for some reason.
>
> If you use psql, does the connection die if you enter the same queries?
>
> Peter
>
> --
> Peter Mount peter@retep.org.uk
> PostgreSQL JDBC Driver: http://www.retep.org.uk/postgres/
> RetepPDF PDF library for Java: http://www.retep.org.uk/pdf/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster




pgsql-general by date:

Previous
From: Rini Dutta
Date:
Subject: Another qs Re: drastic reduction in speed of inserts as the table grows
Next
From: Marek Pętlicki
Date:
Subject: Re: failed sanity check, table answers was not found