tisfy conditions. The same
results with one column type int[] and other column type text or integer.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-bugs mailing list (pgsql
e, you can probably work around it by disabling
fastupdate on these indexes.)
regards, tom lane
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@post
Description:ts_rewrite() causes segfault when query with more than
one node becomes empty
Fixed, thank you
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-bugs
e attached patch does that.
Committed to HEAD, 8.3 and 8.2, thank you. Previous releases are not affected.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-bugs mailing l
I found bug in tsearch2 module (8.3, 8.4).
Thank you, fixed
http://archives.postgresql.org/message-id/20090128183133.0d6f9755...@cvs.postgresql.org
(for 8.3 too)
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW
Looks like this is a dup of #4479:
Yep, exactly
http://archives.postgresql.org/pgsql-bugs/2008-10/msg00094.php
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
--
Sent via pgsql-bugs
Fixed, the reason is the same as for
http://archives.postgresql.org/pgsql-general/2008-10/msg00845.php
Patch:
http://archives.postgresql.org/pgsql-committers/2008-10/msg00187.php
--
Teodor Sigaev E-mail: [EMAIL PROTECTED
Teodor, will you look at this?
Yes, Of course
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
ld allow apostrophe as word
character in replace field, may be in find field too.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
T
Following my -general post about this issue I'm supplying a test case
for a query that fails with a 'Too many LWLocks held' error.
Thank you, I reproduced the bug and now I'm working on it.
--
Teodor Sigaev E-ma
is some other bug involved too. But I would say that compareWORD
is broken nonetheless.
Fixed, you are right.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru
I haven't been able to reproduce it. I think its a race condition
between some of the other processes running at the time. I'm not sure
what else was running on it, but the error suggests an insert to me and
there may have been a vacuum running (plus there are always plenty of
selects running
CREATE INDEX idx_picture_comments_id_tree_gist
ON picture_comments
USING gist
(id_tree);
and the server exited on signal 6 (core dumped)
Is it reproducible? Pls, send to me dump of ltree column.
---(end of broadcast)
But it should dump them as "ALTER whatever" commands, right?
No :(, see
http://archives.postgresql.org/pgsql-hackers/2007-03/msg01112.php
about ALTER OPERATOR CLASS
--
Teodor Sigaev E-mail: [EMAIL
went up in smoke, and I ended up just having have_relevant_joinclause()
Thank you a lot, I was near around it :)
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru
Sorry, versions are 8.2 & 8.3. 8.1 works well
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
---(end of broadcast)---
TIP 9: In vers
VIEW fooview AS
SELECT
f1.a AS a_for_max_b
FROM
foo f1
WHERE
f1.b = (SELECT MAX(f2.b) FROM foo f2);
then all is ok.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.siga
es forward: there is a corner case when
documents has a lot of unique words (millions) and index creation time becomes
very long. 8.2 will create index much faster in this case.
And the performance is swt! Thanks Oleg & Teodor!
:)
--
Teodor Sigaev
that building a gin index on an empty table fails on any
platform. I get a null pointer dereference with the following stack trace
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http
19 matches
Mail list logo
