Re: PANIC: can't juggle and compress too - Mailing list pgsql-bugs

From Dror Matalon
Subject Re: PANIC: can't juggle and compress too
Date
Msg-id 20031029195926.GF2979@rlx11.zapatec.com
Whole thread Raw
In response to Re: PANIC: can't juggle and compress too  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Wed, Oct 29, 2003 at 12:39:57PM -0500, Tom Lane wrote:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
> > Dror Matalon <dror@zapatec.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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgtcl large object read/write corrupts binary data
Next
From: Gaetano Mendola
Date:
Subject: Re: PANIC: can't juggle and compress too