Tom Lane wrote:
Tom Lane <[EMAIL PROTECTED]> writes:
Dror Matalon <[EMAIL PROTECTED]> 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
On Wed, Oct 29, 2003 at 12:39:57PM -0500, Tom Lane wrote:
> Tom Lane <[EMAIL PROTECTED]> writes:
> > Dror Matalon <[EMAIL PROTECTED]> 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 unimp
ljb <[EMAIL PROTECTED]> writes:
> [Using PostgreSQL-7.3.4 and -7.4beta5, Tcl-8.4.x.]
> Binary data written to a Large Object with libpgtcl's pg_lo_write is
> corrupted. Tcl is mangling the data - something to do with UTF-8
> conversion. Example: 0x80 becomes 0xc2 0x80, and 0xff becomes 0xc3 0xbf.
Ian Barwick <[EMAIL PROTECTED]> writes:
> I came across this:
> db=> SELECT 1 FROM object WHERE object IS NOT NULL;
> ERROR: unrecognized node type: 302
Okay, now it says
ERROR: relation reference "object" cannot be used in an expression
regards, tom lane
-
Tom Lane <[EMAIL PROTECTED]> writes:
> Dror Matalon <[EMAIL PROTECTED]> 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-happe
