On Wed, Mar 28, 2007 at 11:36:27AM -0400, Tom Lane wrote:
> Stephen Harris <[EMAIL PROTECTED]> writes:
> > INFO: "sweep_users": found 835831 removable, 972662 nonremovable row
> > versions in 2890304 pages
> Oy, that's one bloated table ... only one live row in every three or so pages.
>
> Prob
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
Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
> 2.6.5-7.244 looks like an older SLES kernel which makes this bug
> suspicially look like one we got reported a while ago:
> http://archives.postgresql.org/pgsql-admin/2006-09/msg00092.php
> and toms analysis:
> http://archives.postgresql.org/pgsql-
Jaime Silvela wrote:
> I completed another migration from 8.1.3 to 8.2.3, and again the problem
> with "unexpected data beyond EOF", exactly twice like before, but in two
> tables different from the last time.
> The kernel bug hypothesis seems a strong one. I told Unix Ops about the
> possible bug,
I completed another migration from 8.1.3 to 8.2.3, and again the problem with "unexpected data beyond EOF", exactly twice like before, but in two tables different
from the last time.
The kernel bug hypothesis seems a strong one. I told Unix Ops about the possible bug, and one of the guys said 2.6.
OK, I've solved my problem... thanks for the hint !
Anyway, just to signal that tsearch2 crashes if SELECT is not granted to
pg_ts_dict (other tables give a proper error message when not GRANTed).On
Fri, 30 Mar 2007 13:20:30 +0200, Listmail <[EMAIL PROTECTED]> wrote:
Hel
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
I recognize the value of working with people who love what they do, that is why
I am looking into the open source community. I am a statistician so I have no
idea about how to find good OSS programmers. Any suggestions are welcomed.
A quantitative hedge fund within Lazard Asset Management in N
The problem I'm trying to solve is pretty standard. I have a table that
records measurements of different types at different times.
CREATE TABLE measurements (
obj_id int4,
val_type_id int4 references lu_val_type(val_type_id),
val numeric,
observation_date date
);
I want a query as simple a
(copy french stem.c and stem.h from the snowball website)
Take french stemmer from
http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/dicts/stemmer/stemmer_utf8_french.tar.gz
At least, it works for me.
Sorry, but Snowball's interfaces are changed very quickly and unpredictable and
Snowball
Ferdinand Gassauer wrote:
On Friday 30 March 2007 10:19:35 Richard Huxton wrote:
Don't forget to cc: the list!
snip
OK this shortens the function, but does not help to "solve" the coalesce
problem
coalecse(empty2null(var1),empty2null(var2),empty2null(var-n))
instead of
coalecse2(var1,var
which version of pgsql exactly?
Listmail wrote:
Hello,
I have just ditched Gentoo and installed a brand new kubuntu system
(was tired of the endless compiles).
I have a problem with crashing tsearch2. This appeared both on
Gentoo and the brand new kubuntu.
I will describe a
Hello,
I have just ditched Gentoo and installed a brand new kubuntu system (was
tired of the endless compiles).
I have a problem with crashing tsearch2. This appeared both on Gentoo and
the brand new kubuntu.
I will describe all my install procedure, maybe I'm doing somet
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
Ferdinand Gassauer wrote:
> Hi!
>
> it would be great to have a coalesce2 function which treats empty strings as
> null values.
I think
COALESCE(NULLIF(value1, ''), value2)
does what you want. You could wrap that in a new function coalesce2 if
you like.
--
Alban Hertroys
[EMAIL PROTECTED]
Don't forget to cc: the list!
Ferdinand Gassauer wrote:
Am Freitag, 30. März 2007 schrieben Sie:
Ferdinand Gassauer wrote:
Hi!
it would be great to have a coalesce2 function which treats empty strings
as null values.
Why? What is the use-case for this?
as far as I have seen, there are a lo
17 matches
Mail list logo
