Csaba Kalman <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Hm, what can you say about the data that goes into the three columns
>> that have hash indexes? I'm going to try testing this with random data,
>> but it'd likely be more useful if I could reproduce your data
>> distribution.
> [ some
Tom Lane writes:
csaba <[EMAIL PROTECTED]> writes:
Here is the CREATE script of the table which is most likely to be one
source of the error. The last error happened after an insert into this
table.
Hm, what can you say about the data that goes into the three columns
that have hash indexes? I
Tom Lane writes:
Csaba Kalman <[EMAIL PROTECTED]> writes:
I frequently get this error message:
PANIC: unexpected hash relation size: X, should be Y
There is no specific point where I get this error, it can occur anytime
after a SELECT/INSERT/UPDATE. I've never got it after DELETE so far.
AFA
csaba <[EMAIL PROTECTED]> writes:
> Here is the CREATE script of the table which is most likely to be one
> source of the error. The last error happened after an insert into this
> table.
Hm, what can you say about the data that goes into the three columns
that have hash indexes? I'm going to try
Csaba Kalman <[EMAIL PROTECTED]> writes:
> I frequently get this error message:
> PANIC: unexpected hash relation size: X, should be Y
> There is no specific point where I get this error, it can occur anytime
> after a SELECT/INSERT/UPDATE. I've never got it after DELETE so far.
AFAICS this shou
Hi,
I'm using Postgres 8.2.2 on Windows.
I frequently get this error message:
PANIC: unexpected hash relation size: X, should be Y
There is no specific point where I get this error, it can occur anytime
after a SELECT/INSERT/UPDATE. I've never got it after DELETE so far.
When it occurs, the s
