Re: [BUGS] PANIC: can't juggle and compress too

#1

Dror Matalon <dror (AT) zapatec (DOT) com> writes:

Quote:

Oct 28 01:04:50 ... postgres[7572]: [52227-1] PANIC: can't juggle and compress too

Oh? I don't suppose you have a way to reproduce this :-(

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

#2

On Tue, Oct 28, 2003 at 02:55:17PM -0500, Tom Lane wrote:

Quote:

Dror Matalon <dror (AT) zapatec (DOT) com> writes:
Oct 28 01:04:50 ... postgres[7572]: [52227-1] PANIC: can't juggle and compress too

Oh? I don't suppose you have a way to reproduce this :-(

No not really. It's been running for a few hours without any problems.
Looks like after this happened the database shut down all processes and
then did a "recovery."

What does the error message mean?

Regards,

Dror

Quote:

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

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

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

#3

Dror Matalon <dror (AT) zapatec (DOT) com> writes:

Quote:

On Tue, Oct 28, 2003 at 02:55:17PM -0500, Tom Lane wrote:
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. It'd be a lot easier to figure out what's wrong if I could
reproduce the failure ...

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

#4

Tom Lane <tgl (AT) sss (DOT) pgh.pa.us> writes:

Quote:

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.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

#5

On Wed, Oct 29, 2003 at 12:39:57PM -0500, Tom Lane wrote:

Quote:

Tom Lane <tgl (AT) sss (DOT) pgh.pa.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

Quote:

regards, tom lane

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

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

#6

Tom Lane wrote:

Quote:

Tom Lane <tgl (AT) sss (DOT) pgh.pa.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.

Less dangerous then this:

http://mathworld.wolfram.com/RoundoffError.html

:-O

Regards
Gaetano Mendola

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: [BUGS] PANIC: can't juggle and compress too

mailing.database.pgsql-bugs mailing.database.pgsql-bugs

Re: [BUGS] PANIC: can't juggle and compress too - 10-28-2003 , 01:59 PM

Re: [BUGS] PANIC: can't juggle and compress too - 10-28-2003 , 02:19 PM

Re: [BUGS] PANIC: can't juggle and compress too - 10-28-2003 , 02:41 PM

Re: [BUGS] PANIC: can't juggle and compress too - 10-29-2003 , 11:43 AM

Re: [BUGS] PANIC: can't juggle and compress too - 10-29-2003 , 02:02 PM

Re: [BUGS] PANIC: can't juggle and compress too - 10-29-2003 , 06:03 PM