Re: MemoryContextAlloc: invalid request size 1934906735

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: MemoryContextAlloc: invalid request size 1934906735
Date: 2002-08-29 03:07:05
Message-ID: 12754.1030590425@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"D'Arcy J.M. Cain" <darcy(at)druid(dot)net> writes:
> Hmm. I did give it a harder look and look what jumped out. Both
> chkpass_out and chkpass_rout return PG_RETURN_CSTRING but chkpass_out
> builds a standard c string while chkpass_rout builds a variable text
> structure. That can't be right.

It's not, but chkpass_rout is declared to return text, so it should be
saying PG_RETURN_TEXT_P. It turns out both macros do the same thing,
so this is just a cosmetic issue.

> Oh, one more datapoint - the error only happens on vacuum analyze, not just
> vacuum. Not sure what that means exactly.

That is odd. You only have the chkpass operators shown in the contrib
module, right? No "chkpass = chkpass" operator? Without one, vacuum
analyze should pretty much ignore the chkpass column ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-08-29 03:11:14 Re: Postgres problems
Previous Message control 2002-08-29 02:44:10 Inquiry From Form [pgsql]