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

Re: Yikes! Bitten by line length?

From: Ken Corey <ken(at)kencorey(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Yikes! Bitten by line length?
Date: 2001-01-16 15:44:39
Message-ID: 3A646C67.CB01AD4D@kencorey.com (view raw or flat)
Thread:
Lists: pgsql-novice
Tom Lane wrote:
> Ken Corey <ken(at)kencorey(dot)com> writes:
> > GRE=# select
> > I_SESSION(null,'54',2,'E2K','0x577A977F7FCCBF5A567C6097A5A5A9D47DA39B82298C6E9F89DA4D4F67E39B856692DDAA8A938E637D7F6C7000000000000000000000000000000000000000000000000000000000000000000');
> > GRE'# '
> > GRE-# );
> > ERROR:  parser: parse error at or near
> > "0000000000000000000000000000000000"
> > GRE=#
> 
> > [Note that the final ' wasn't found, so I had to add it, and then close
> > the parenthesis and execute the whole mess with the semi colon.]
> 
> That's pretty odd; you seem to have a broken psql.  What PG version are
> you running?  Do you have libreadline (history support) in there, and if
> so what libreadline version is it?

I downloaded pg 7.0.3, untarred it, went into the directory, typed:

configure
make
make install

No libreadline (though I should get it...I'd like to have up-arrow to go
back to previous lines in psql!)

Any other ideas?  

I've downloaded 7.1b3 to try out. Since I won't have any real critical
data in there until March timeframe, I can afford to play with the
latest version. If that fixes it, I'll report back to this list.

-Ken

In response to

Responses

pgsql-novice by date

Next:From: TamsinDate: 2001-01-16 15:59:21
Subject: RE: log file?
Previous:From: RasputinDate: 2001-01-16 15:29:12
Subject: Re: Unix Scripts linking with Postgres

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