Re: MemoryContextAlloc: invalid request size 1969649011

hi tom,
> > sometimes drops this error:
> > DBD::Pg::st execute failed: ERROR: MemoryContextAlloc: invalid request
size
> > 1969649011
>
> This looks to me like a corrupted-data issue --- specifically, the
> length word of some data value in the table has gotten clobbered and
> now appears ridiculously large.
>
> You should try to determine exactly which row(s) contain bad data.
the error only occurs sometimes. if some rows had been corrupted shouldnt it
be reproduceable?
anyway, i try a dump/restore. it should fail when the table has corrupted
rows...

regards

Thilo Hille
thilo(at)resourcery(dot)de

----- Original Message -----
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thilo Hille <thilo(at)resourcery(dot)de>
Cc: <pgsql-novice(at)postgresql(dot)org>
Sent: Thursday, August 08, 2002 4:25 AM
Subject: Re: [NOVICE] MemoryContextAlloc: invalid request size 1969649011

> "Thilo Hille" <thilo(at)resourcery(dot)de> writes:
> > this query...:
>
> > my $tsql = qq{ insert into user_month (select '$currentmonth'::date as
> > month,'*nopleid*',count(distinct uuid) from user_log where
day<=now()::date
> > and day>(now()-interval '30 days')::date) };
> > my $tsth = $tdbh->prepare( $tsql );
> > $tsth->execute();
>
> > sometimes drops this error:
> > DBD::Pg::st execute failed: ERROR: MemoryContextAlloc: invalid request
size
> > 1969649011
>
> This looks to me like a corrupted-data issue --- specifically, the
> length word of some data value in the table has gotten clobbered and
> now appears ridiculously large.
>
> You should try to determine exactly which row(s) contain bad data.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>