Fixes are committed to CVS, hope, they will help you.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
---(end of broadcast)---
TIP 9: In versi
with
the imagination that it is, therefore, obscure and, on the contrary, that
what is to prove it is clear, and so we understand it easily.
41. Epigrams of Martial.--Man loves malice, but not against one-eyed men nor
the unfortunate, but against the fortunate and proud. People are mistaken in
thi
to the rich, that, if they do it not in the sight of God, they
depart from the command of religion.
SECTION VI: THE PHILOSOPHERS
339. I can well conceive a man without hands, feet, head (for it is only
experience which teaches us that the head is more necessary than feet).
believe that matters were reversed? In short, as we often dream that
we dream, heaping dream upon dream, may it not be that this half of our
life, wherein we think ourselves awake, is itself only a dream on which the
others are grafted, from which we wake at death, during which we have as few
princ
I think I found at least one part of the problem. I was able to
reproduce a crash similar to yours by running the german_ispell
dictionary against long random words, and what I found out is that
it's possible to overrun the fixed-length "buf" buffer declared at
line 1542 of spell.c.
Run till exit
Tom Lane wrote:
This is not the same test data as in your previous concurrent-index
problem, then? I still had a copy of that, so I tried the case, and
it doesn't crash on that data ...
Teodor Sigaev wrote:
I tryed to reproduce the bug but without success.
Could you provide a dump of text col
Hannes Dorbath <[EMAIL PROTECTED]> writes:
> Alvaro Herrera wrote:
>> Can you please provide a backtrace from gdb?
> I hope that contains it: http://theendofthetunnel.de/backtrace.log
Hmmm --- one thing that jumps out at me is that SplitToVariants assumes
(in four places) that the SplitVar.stem a
Hannes Dorbath <[EMAIL PROTECTED]> writes:
> Crash happens about 7 minutes after issuing the UPDATE statement with
> current CVS HEAD. The table has around 5 million rows. It's always
> reproducible.
This is not the same test data as in your previous concurrent-index
problem, then? I still had
I tryed to reproduce the bug but without success.
Could you provide a dump of text column?
Hannes Dorbath wrote:
Crash happens about 7 minutes after issuing the UPDATE statement with
current CVS HEAD. The table has around 5 million rows. It's always
reproducible.
--
Teodor Sigaev
Hannes Dorbath <[EMAIL PROTECTED]> writes:
> Hannes Dorbath wrote:
>> Yes, I'll try to catch the row.
> I just slammed a BEFORE UPDATE FOR EACH ROW trigger with RAISE NOTICE on
> the table to catch the row ID where it fails.
> The row ID is never the same. Neither can I reproduce it when I use t
Hannes Dorbath wrote:
> Hannes Dorbath wrote:
>> Yes, I'll try to catch the row.
>
> I just slammed a BEFORE UPDATE FOR EACH ROW trigger with RAISE NOTICE on
> the table to catch the row ID where it fails.
>
> The row ID is never the same. Neither can I reproduce it when I use the
> last reported
Hannes Dorbath wrote:
Yes, I'll try to catch the row.
I just slammed a BEFORE UPDATE FOR EACH ROW trigger with RAISE NOTICE on
the table to catch the row ID where it fails.
The row ID is never the same. Neither can I reproduce it when I use the
last reported row ID.
Is NOTICE logging / pr
Alvaro Herrera wrote:
Can you please provide a backtrace from gdb?
I hope that contains it: http://theendofthetunnel.de/backtrace.log
It'd be nice to have text string which cause segfault and sql script for
configuration.
Yes, I'll try to catch the row.
--
Best regards,
Hannes Dorbath
-
It'd be nice to have text string which cause segfault
and sql script for configuration.
Oleg
On Tue, 15 Jan 2008, Hannes Dorbath wrote:
Crash happens about 7 minutes after issuing the UPDATE statement with current
CVS HEAD. The table has around 5 million rows. It's always reproducible.
ISpell
Hannes Dorbath wrote:
> test=# UPDATE test SET tsv = to_tsvector(text);
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> Jan 15 11:32:50 brainchild postmaster[14815] general protection ri
Crash happens about 7 minutes after issuing the UPDATE statement with
current CVS HEAD. The table has around 5 million rows. It's always
reproducible.
ISpell dict used:
http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/dicts/ispell/ispell-german-compound.tar.gz
(iconved to UTF-8)
Welcom
16 matches
Mail list logo
