Re: PANIC: can't juggle and compress too

From: Dror Matalon <dror(at)zapatec(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: PANIC: can't juggle and compress too
Date: 2003-10-29 19:59:26
Message-ID: 20031029195926.GF2979@rlx11.zapatec.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Oct 29, 2003 at 12:39:57PM -0500, Tom Lane wrote:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> > Dror Matalon <dror(at)zapatec(dot)com> writes:
> >> Oct 28 01:04:50 ... postgres[7572]: [52227-1] PANIC: can't juggle and compress too
>
> >> What does the error message mean?
>
> > It's an unimplemented case in FSM memory management. I thought that
> > it was a can't-happen case; either I was wrong and it does need to be
> > implemented, or there's a bug elsewhere that's triggering the failure
> > condition.
>
> I've concluded that that case does need to be handled; I think it can
> arise in situations where a relation's allocated share of FSM space
> decreases due to roundoff error. Fix committed accordingly.

The best support money can't buy. One more reason to love Postgres.

Thanks Tom,

Dror

>
> regards, tom lane

--
Dror Matalon
Zapatec Inc
1700 MLK Way
Berkeley, CA 94709
http://www.zapatec.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Gaetano Mendola 2003-10-29 23:58:24 Re: PANIC: can't juggle and compress too
Previous Message Tom Lane 2003-10-29 18:33:09 Re: pgtcl large object read/write corrupts binary data