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

From Tom Lane
Subject Re: PANIC: can't juggle and compress too
Date
Msg-id 15424.1067449197@sss.pgh.pa.us
Whole thread Raw
In response to Re: PANIC: can't juggle and compress too  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PANIC: can't juggle and compress too
Re: PANIC: can't juggle and compress too
List pgsql-bugs
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.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Rod Taylor
Date:
Subject: Re: [HACKERS] Autocomplete on Postgres7.4beta5 not
Next
From: Tom Lane
Date:
Subject: Re: Minor beta buglet "unrecognized node type: 302"