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

Yikes! Bitten by line length?

From: Ken Corey <ken(at)kencorey(dot)com>
To: "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org>
Subject: Yikes! Bitten by line length?
Date: 2001-01-16 00:05:37
Message-ID: 3A639051.601303EF@kencorey.com (view raw or flat)
Thread:
Lists: pgsql-novice
Hi All.  Happy Monday..;^)

I've now got my app converted from using sybase to using PostgreSQL. 
Got the first successful compile today.  However, that doesn't mean it
works.

I'm getting some strange core dumps, so I went through my logs, and it
turns out that the core dumps are happening after this sql is attempted:

select
I_SESSION(null,'54',2,'E2K','0x577A977F7FCCBF5A567C6097A5A5A9D47DA39B82298C6E9F89DA4D4F67E39B856692DDAA8A938E637D7F6C70A679A67AA881D68926976C966CB5A0B48E793795472F216B4A652933406A2B5B4554660B5734765B3A623A5421A02D2B5E5B5916008B4E6012106A0A3258291D123C1F6B4A341EF82152673435512D243158561B1520582463622363702F2640DD9A6B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000');

I know about the 8K limit for a row but this isn't even close. So, I
went into psql to try to run this query by hand: 

GRE=# select
I_SESSION(null,'54',2,'E2K','0x577A977F7FCCBF5A567C6097A5A5A9D47DA39B82298C6E9F89DA4D4F67E39B856692DDAA8A938E637D7F6C70A679A67AA881D68926976C966CB5A0B48E793795472F216B4A652933406A2B5B4554660B5734765B3A623A5421A02D2B5E5B5916008B4E6012106A0A3258291D123C1F6B4A341EF82152673435512D243158561B1520582463622363702F2640DD9A6B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000');
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.]

At any rate, this is not the error message I'd have expected.  It seems
that the input buffer is wrapping around the end, and so the whole
string isn't being processed properly.

Am I doing something silly?

-Ken

Responses

pgsql-novice by date

Next:From: John PoltorakDate: 2001-01-16 01:18:03
Subject: Sample databases
Previous:From: Anthony E . GreeneDate: 2001-01-15 21:13:22
Subject: Re: Re: Postgres access using PHP

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